v0.2.0 — install & integration overhaul (npm + first-run + status)

The install & integration overhaul — OpenFusion is now on npm, with first-run hand-holding, a status surface, and the silent footguns fixed.

Added

• Published to npm → npx -y openfusion-mcp works with no clone or build. Every client snippet now defaults to it.
• npx openfusion-setup — interactive installer that picks your MCP client, writes the correct config snippet (claude mcp add, ZCode mcp.servers, Cursor .cursor/mcp.json, Zed context_servers, Codex mcp_servers, Gemini-CLI family, Cline, Claude Desktop…), and offers to install the agent skill. One command end-to-end.
• First-run UX — on a fresh install the server prints a stderr banner (version, data path, configured status) and opens the dashboard automatically when a display is present. No more "where do I configure?" mystery.
• GET /api/status — one lightweight call returning { version, home, configured, reasons?, firstRun, dbPath } for the dashboard, agents, and CLI health checks.

Changed / Fixed

• GET /api/health now also returns version + configured (still ok:true for back-compat).
• Version is no longer hardcoded — read from package.json via a shared helper; the MCP handshake reports the real version (was stale at 0.1.0).
• Config upgrades print a notice — a v1→v2 migration on load now logs a one-time stderr message so you know a restart-after-update happened.
• better-sqlite3 native-addon failures are now actionable — a clear "run npm rebuild better-sqlite3" message with toolchain requirements, instead of an opaque MODULE_NOT_FOUND stack trace.
• Docs: README leads with npx; documents OPENFUSION_HOME (and that it prints on startup), the native-build requirement + recovery, an Updating section, and the client tool-call-timeout caveat.

Install (the new way)

npx openfusion-setup        # interactive: writes client config + installs skill
# then restart your MCP client — `fusion` + `open_dashboard` are available

Or manually point any MCP client at npx -y openfusion-mcp. 50 tests green. Full changelog: CHANGELOG.md.

npm publish note: the GitHub side (code, tag, this release) is live; the npm publish itself requires a one-time password from the maintainer and runs separately.