AssertLedger 1.4.0

AssertLedger 1.4.0

This minor release changes a public CLI contract: assertledger analyze now refuses an option it does not know. It writes the usage to stderr, nothing to stdout, and exits 64, as init and doctor already do. It used to ignore the option, so analyze . --exclude .claude exited 0 on the full set while looking as if the exclusion were applied: --exclude belongs to doctor and init.

Migration: drop the option. To leave an entry out of the analyzed set, declare it with assertledger init --exclude NAME, which records it in assertledger.config.json for analyze to honor. --json stays accepted, and analyze, analyze <repository>, analyze <repository> --json and analyze --json <repository> are unchanged. An argument that starts with - is an option, so a repository directory whose name starts with - is passed as ./-name.

Unchanged: reason codes, schemas, digests and MCP tool schemas. A second positional argument is still ignored, and so is an option placed before the command.

Release identity: 9327ce8ab757cd03848416bc517f96de333c0411. The tag points at the commit the package was built from, not at the merge commit (8949ef810b1dc2ecea4c83c5250aace826a365a6) that carries the same tree. The published assertledger-1.4.0.tgz (SHA-256 f389f06b5f1a240bdb172b58a442fcdd7ba5eba710b06f6831c008b03aca2931, npm shasum affe5ee78458537803f6fb71aaa020e41b5bdd51) was reproduced byte for byte by a local build from a clean checkout of that commit. The package records that commit and a clean source tree. The release preparation pull request (#30) passed 13 of 13 checks, and its independent proof audit and deterministic gate are recorded there. Installed from the registry, the package exits 64 on analyze . --unknown and on analyze . --exclude .claude.

Install with npm install --save-dev assertledger@1.4.0. See the changelog.