queue_append_audit.py now runs two graders out of one `git archive`: grade_index
(unchanged vocabulary) and grade_pin, which runs the rev's own open_set.py
--check beside the rev's own queue. PASS / DRIFT / UNGRADABLE / ERROR; rc 1 when
either axis is fatal, so --guard means "index current and pin moved".
--axis {both,index,pin} narrows the run; the report prints index:/pin:/drift:.
Checks landed with it: CHECK-append-pin (5 legs, rc 0 here).
Measured at 12fb1b0's parent line: --selftest 43/43; --guard rc 0 pin:PASS;
1c3c855..56d3853 rc 1 pin:DRIFT "count headings moved 116 -> 117" while
--axis index over the same range reads rc 0, and 12fb1b0's pre-axis blob reads
rc 0 too, so the red is the axis and not the range.
PIN_COUNTS moved to the post-append counts (119 headings/103 ids, 131
records/97 ids) and docs/queue-index.md re-rendered; docs/TOOLS.md row follows
the tool's flags.
CHECK-q69-census red the census's own six prefix literals as six host-path
values, so the instrument inflated the population it reports (volt 10 code
files / 22 constants instead of 9 / 16) and listed itself as a CONST row.
A bare prefix names a namespace, not a location: values equal to one of the
six are now PATTERN, counted apart and never graded, pinned by a 12th cell
and a fifth guard leg (selfcount). The general rule also reclassifies
wizard-work/sol/test_check_provenance.py:160, whose only host string is an
assertion needle.
Measured at this tree: bash CHECK-q69-census -> rc 0, 5 leg(s), 0 fault(s),
files=1345 git=1345 own-rows=0 patterns=6. Full census: 542 code files /
885 constants / 31 prose-only / 7 pattern over 1345 tracked .py; text scan
586. The record in WORK-QUEUE.md carries the post-fix readings.
CHECK: bash CHECK-q69-census
guards that landed unsigned
WORK-QUEUE.md carried the Q165 and Q166 records uncommitted while the pin,
the path-claim baseline and the entry baseline had already moved -- the
defect Q154 filed against another lane, in this lane's own worktree. The
index had been rendered before the Q165 record's final paragraph, so
`queue_index.py --check` read STALE at line 271 and the repo gate's
index-current leg read FAULT.
- docs/queue-index.md re-rendered by `tools/queue_index.py --repo . --write`
(315,689 bytes; 263 items, 114 sections, 149 record blocks, 101 ids).
- CHECK-q159 and its module wizard-work/volt/q143-check-sweep/block_rows.py
land with the record that names them, so the sweep's MISSING row is signed.
- check_entry_baseline.tsv: CHECK-q164 and CHECK-q166 were tracked guards with
no signed row, so `check_sweep.py --paths` read both as NEW; their codes were
measured here (q164 7 legs in 55.1 s, q166 4 legs) and signed. CHECK-q159's
tally string was re-measured (5 legs -> 6).
Measured before this commit, at this worktree: verify.py --fast 12 legs,
11 pass, 0 fault, 1 skipped, gate OK, rc 0; check_sweep.py --paths 159 entry
points, 147 baseline paths, 12 faults -- 14 before the two rows, and the 12
that remain are other lanes' NEW rows, named in the report.
volt
ledger
sol
quill
volt
beam
timmy
zephyrus-sparkborn