[ruvnet]

Fixes #5.

What was broken (reproduced from a fresh registry install of 0.3.3)

Entry	0.3.3
require("lean-agentic")	fails: Cannot find module '../wasm/leanr_wasm.js'
import "lean-agentic"	fails: ERR_MODULE_NOT_FOUND .../wasm/leanr_wasm.js
import "lean-agentic/node"	fails: dist/node.mjs is a copy of the CommonJS file (require is not defined)
require("lean-agentic/node")	works, but prints Initializing Lean-Agentic WASM... and per-call logs to stdout
MCP server	stdout gets Initializing Lean-Agentic WASM... as soon as a tool runs, which breaks JSON-RPC
lean-agentic mcp start	exits without serving anything (requiring server.js skips its require.main start)

Changes

• Root entry now points at the Node.js build (same API as lean-agentic/node, plus init()), instead of the bundler-target wasm/ that was never published. Browsers use lean-agentic/web; the README platform table now says so.
• ESM: scripts/build.js writes real ESM wrappers for dist/node.mjs and dist/index.mjs (they load the CommonJS build through createRequire, so both module systems share one WASM instance).
• Logs: the logs came from web_sys::console::log_1 in leanr-wasm. They are now off by default, go to console.error (stderr) when on, and are controlled by LEAN_AGENTIC_DEBUG=1 or setDebug(true). wasm-node/ and wasm-web/ are rebuilt from source with wasm-pack --release (public WASM API unchanged apart from the new setDebug; each .wasm is about 2 KB smaller).
• MCP server: sends console.log/info/debug to stderr, no longer answers notifications such as notifications/initialized, and exports startServer(), which lean-agentic mcp start now calls.
• package.json: exports adds ./package.json; files drops the unused wasm; build:wasm builds the nodejs and web targets that ship; prepublishOnly runs build:js only, so the published tarball is the one CI tested. Version 0.3.4.
• Types: .d.ts files match the real API (getStats, benchmarkEquality, setDebug, init on the root entry). Checked with tsc --strict --module nodenext.
• CI: the npm job now packs the package, installs the tarball into a temp project, and runs scripts/check-package.mjs. The script requires and imports every entry point (., ./node, ./web, ./package.json), requires that each prints nothing to stdout, runs the CLI, and drives the MCP server (directly and through lean-agentic mcp start) with initialize, notifications/initialized and two tools/calls that construct the WASM demo. It then asserts that the first stdout line is the initialize result and that every stdout line is JSON-RPC. Run against the registry 0.3.3, 9 of its 12 checks fail. Run against this branch's tarball, all pass.

Not in scope (still open)

• benchmarkEquality() throws unreachable in WASM because it uses std::time::Instant. This is a separate issue that already exists in 0.3.3.
• The README's Ed25519 example (AgentIdentity, SignedProof, ProofConsensus from require('lean-agentic')) lists symbols the npm package does not export.
• initialize reports capabilities as booleans (tools: true). The MCP spec expects objects.

🤖 Generated with claude-flow