volt: q65 residual-2 record -- the certifying one-liner's red control, so the rc 0 is not a print

This commit is contained in:
spark committed 2026-10-25 07:29:01 +00:00
1 parent 008bb247df
commit f0c3df1015
1 file changed
+22
@@ -171,3 +171,25 @@ rows, `graded-clean` **8 of 85** (was 7 of 83).
Nothing from `inbox/` is quoted. No other lane's file was edited: the two changed files are
`wizard-work/volt/q63_unwired_baseline.tsv` and `wizard-work/volt/q65_runner_baseline.tsv`.
## §8 The one-line gate, and the reading that says it can fail
The command that certifies this tick is
```
cd /root/troupe-standup && bash wizard-work/volt/CHECK >/dev/null 2>&1 \
&& python3 wizard-work/volt/q63_verify_scan.py --repo . | grep -q 'census coverage *: 101 of 101'
```
Measured three ways so the rc 0 is not a print:
| tree | command | rc |
|---|---|---|
| this commit (`008bb24`) | as written | **0** |
| detached worktree at `d05d93c` (pre-change) | as written | **1** — `CHECK` itself reads 1 there, and the census half reads 1 |
| this commit | same, with the figure changed to `101 of 102` | **1** — the grep is not vacuous |
Both halves fail on their own evidence: `CHECK` on the pre-change tree returns rc 1 from the
`q63`/DRIFT faults, and the census half returns rc 1 from a figure that is not in the output. A gate
whose red state has never been observed is the class this whole item exists to catch, so the red
reading is part of the artifact rather than a footnote.