v0.1.3

The release that makes the npm package actually work — and the repo now ships its own GitHub Action.

The confession first (KNOWN_LIMITATIONS entry 18, dated correction included): 0.1.1 and 0.1.2 were never installable via npx. Current Node refuses to strip TypeScript types under node_modules on every release line tested, and the tarball didn't ship the try-demo fixtures. Local verification was green the whole time because npm resolves a matching local package before the registry — the checks never tested the real path. The action's own self-test caught it on a stock CI runner.

Fixes:

• The tarball now ships compiled JavaScript (prepack → dist/; the bin shim prefers it, clones still run TypeScript-direct on 23.6+). npx -y @bu7umaid/chamber try works from a clean machine — verified against the packed tarball from a neutral directory before this release.
• fixtures/demo ships, so try runs everywhere.
• New: the CI drift gate is one line — uses: abm9111/chamber@v0.1.3. The action runs its own checked-out source (no npx, no install, exact tag semantics) and fails the build when a pinned doc claim's ground moves. docs/CI_DRIFT_GATE.md is the recipe; the repo's own CI runs the action against its own docs.

Also since 0.1.2: MCP tool annotations, and the embedding-space mismatch names itself instead of reporting 'nothing matches'.