Amabie 2.0.1 — verification session fixes

Claude requests can now register through a session-bound CLI command while project MCP approval is pending. Recognized agent calls cannot reseal verification, accept their own work or directly replace authority and hook files. Open sessions require administrative confirmation in a human terminal.

npm install --global amabie-cli@2.0.1
amabie setup --yes

Requires Node.js 22+, npm and Git. The package is amabie-cli; the command is amabie.

The onboarding implementation now has separate configuration, execution, proof, evidence and session modules. CLI commands call those owners directly. Productization runs the full unit suite once, removing 32 redundant invocations without removing test cases. Version tags run the complete CI matrix once through the protected release workflow.

The shorter README and npm landing page lead with a reviewed failing test, then agent implementation. Existing NOT PROVEN semantics remain intact. New worker-written tests carry an evidence-origin caveat; rewriting existing checks is treated more strictly. Missing evidence is not a pass.

Workflow guide · Reproducible upstream demo · npm package

The demo uses pinned escape-html source and original upstream tests, with a simulated agent completion. It is not a live-model comparison or a real-world false-positive measurement. Historical token-saving claims remain withdrawn.

Source: 18e4da69e59297fb957e3b007a733155e1b2c7d5. The source CI contains Windows/Linux core suites, three standalone builds and the designated Axios proof. All six source CI jobs passed. Host-bound and cost-gated skips are reported separately; macOS standalone evidence is not a full native macOS suite.

The attached clean-room-tested artifact is amabie-cli-2.0.1.tgz, 304,787 bytes. SHA-256: 52e1e530b47159d03d1683af3235ae3e058d11e1bdd6de96702d4e56de3bc0a6.

Publication uses the npm trusted publisher restricted to criptofn/Amabie, release.yml and amabie-release. Default capability remains LOCAL, sharing one OS user. The session guards do not provide an OS sandbox or general HARDENED isolation.