Repository navigation
v0.8.1
A verify cleans up after itself on every exit and keeps its scratch on disk, no
shipped script pipes into grep -q, and every figure in the docs is rendered
from its source.
Changed
- Every figure in the README and the docs is rendered from its source, never
typed. A number that describes the project is a marker,
<!-- fig:NAME -->VALUE<!-- /fig -->, thatscripts/render_figures.pycounts
from the tree. The suite size and the lesson count are a rounded floor ("1,300+",
"110+"), so a pull request that adds a test or a lesson no longer hand-edits three
to five lines; backends, evals, denied verbs, profiles, user stories and gaps stay
exact and are rendered too.--checkrefuses a stale marker, an unknown name, a
malformed or nested marker, a marker in a code fence, a figure typed outside a
marker, a site that stopped stating its figure, a tree with no markers and a
source it could not read;--writerepairs stale values and is idempotent.
check_claims.shandcheck_drift.py readme-countscount through the same module
and no longer match typed numbers, the hook and CI run the figure check, and the
drift cases that mutated literal counts mutate marker contents. Two drift tests
had gone vacuous because they matched the literal 110.
Fixed
- A verify no longer leaves the pull request behind (#111). The extracted
tree and its cargo target now live under$STATE/verify-workon disk, and one
EXITtrap removes them on every exit, a refusal included. On a tmpfs/tmp
two refused verifies had kept 12 GB in RAM and pushed the next verify's rustc
past its container's memory limit (lesson 115). - No shipped script pipes into
grep -q(lesson 116). Four sites read a
match as a failure wheneverpipefailsaw the writer take SIGPIPE: fixup's
sign-off check (seen flaking), prune's open-PR keep test, the doctor's timer
check and fixup's test-count check. The suite now refuses the shape anywhere
inbin/,lib/, the installers and the verify suites.