release-npm-versionlisted

# Release an npm Version `npm publish` is irreversible after 72 hours and ships to everyone who installs the package. This card is the gate that catches the usual release breakers (missing `dist`, a CLI that won't start, an MCP server that won't speak stdio) **before** they reach users. ## When to use Before bumping the version and running `npm publish`. ## Procedure 1. **Build.** `npm run build` (runs `tsc` + copies dashboard static assets). Zero errors. 2. **Test.** `npm test` — all tests green. (`test` already runs `build` first.) 3. **Pack smoke test.** `npm pack` to produce the tarball. Inspect its contents: ``` tar -tzf claude-amplifier-<version>.tgz ``` Confirm it includes `dist/`, `README.md`, `CHANGELOG.md`, `CLAUDE.md`, `LICENSE`, and `examples/` — and **excludes** `node_modules/`, `*.db`, `tests/`, and source `.ts`. Match this against the `files` field in `package.json`. 4. **Fresh temp-install test.** In a clean temp dir, install the packed tarball (not the workspace), e.g.: ``` npm i -g ./claude-amplifier-<version>.tgz # or into a temp project ``` This catches "works on my machine" issues (missing files, native `better-sqlite3` rebuild problems). 5. **Verify CLI starts.** `claude-amplifier help` and `claude-amplifier doctor` run and print sane output from the installed binary. 6. **Verify MCP stdio starts.** Launch the server in MCP mode (`claude-amplifier mcp`) and confirm it speaks MCP over stdio — e.g. i