Repository navigation
0.7.2
[0.7.2] — 2026-10-26
A patch about the release process itself: the checks that decide whether a
release is coherent now live in one command and run in CI.
Added
npm run release:check. It comparespackage.jsonwith both versions
inpackage-lock.json, the first release heading in this file, an optional
tag, and the filesnpm pack --dry-runwould publish.--releaserequires
the CHANGELOG heading;--tag v<version>requires the tag. It is part of
npm run selfcheck, runs in the test job without--release, and runs in
the publish job with the pushed tag.
Fixed
CONTRIBUTING.mdasked for two commits and two tags.npm version
already makes both by default, and the steps after it made a second one. The
release steps now usenpm version --no-git-tag-version, verify the tree
before committing, and tag once.models.ymlclaimed a check it did not run. The scheduled job reads
catalogue lifecycle; it cannot see a route that answers 200 with no text.
The comment now says so and nameseval/models.mjs --free --check.- README named
doctoras the pre-release check. It is the online check.
npm run selfcheckis the release gate, and the README now says which is
which.
Documentation
MIGRATION.mdcovers 0.4.x → 0.7.x. The config file format survives, but
the compiler now owns more keys:runis build + verify,--reviewexits 5
on a rejected review, thebuildcap is 120,docandverifyno longer
open bash with"*": "allow", denied tool calls are not retried, the
reviewer moved off the retirednemotron-3-ultra-free, anddoctor --check-modelschecks lifecycle rather than presence.