Repository navigation
0.7.1
[0.7.1] — 2026-10-26
A release about checks that were green while the thing they check was not:
a withdrawn model reported healthy, a lane on a model that cannot do the
lane's job, a config from the previous kit reported as matching the current
profile, and a free route that answered nothing still recommended as a
candidate.
Fixed
doctor --check-modelsread presence, not lifecycle. models.dev keeps
a withdrawn model and marks itdeprecated; the check only asked whether a
record existed, so a pulled base or fallback rung was reported healthy.
It now asksisWithdrawn, and the message says withdrawn-or-removed.- A lane's route was never checked for the job it does. A live model that
cannot call tools, avisionlane on a text-only model, a missing context
or output ceiling, and an effort level the model cannot express all passed
doctor. Each is now reported by lane, against the first live rung of the
chaininstallwould use. A level that snaps down is still allowed, because
that is the documented behaviour; a level that resolves tonullis not. verifycompared a hand-written key list.harness.kithad been added
to the compiler and not to the list, so the live install - compiled by
0.6.4, still carrying 25 ECC subagents - passed as matching the profile.
The check now recompiles the profile over the installed file and compares
every key the compiler owns. A config from an older kit is a note;
verify --strictmakes it a failure.- The probe could not tell an answer from a spent route.
eval/models.mjs
now classifiesok,empty,timeoutanderror, treats a finished step
with no text asempty, and exits non-zero under--check. - A free route that answered nothing was still recommended. Two live
probes ofnemotron-3-ultra-freeproduced no step and no text. The route
is recorded ineval/unusable-models.json;--freeandresearchskip it
until it is re-probed, and the standalone profile and its reviewer rung are
retired. The reviewer lane now runs on GLM 5.3 Flash.
Added
eval/models.mjs --free --listselects live free routes without spending a
request and names the ones a probe rejected.eval/graph.mjschecks the import graph and prints the routing graph:
--checkfails on an unresolved import, a module cycle, or a source file no
entry or test reaches;--routingprints profile -> lane -> model with the
catalogue's verdict on each rung.--jsonand--dotare for a machine.npm run graph,npm run test:coverage(85% lines, 70% branches, 80%
functions), andnpm run selfcheck, which runs build, typecheck, the suite,
the graph,premises, and a fresh install in a temporary config directory
ending inverify --strict.test/effort.test.jscovers the config mutation directly: the router's
session model, a lane's preserved model and prompt, anullvariant
deleting a stale one,harnesskeys surviving, and health entries keyed by
provider.test/trust.test.jscovers a replacement that fails after the
revoke and has to say the package now has no publisher.- CI runs
graph,test:coverageandpremisesbeside the suite, and the
install smoke test usesverify --strict. A dailymodels.ymljob asks the
live catalogue whether every shipped model is still live.
Changed
fleet-safeandfleet-allare refreshed against the live catalogue:
fleet-safepublishes three effort levels (low,high,max) and
fleet-allno longer claims image attachments on a model that does not
read them.- README and
docs/ROUTING.mdquote the current fleet: reviewer on GLM 5.3
Flash, build and longform on Flint, and the seven lanes that move under the
zero-retention ceiling.