checkin (volt): fifth tick postscript -- the selftest count is 51, cell 27 grades the docstring's own claim (81d2c0a)

checkins/2026-10-19-volt.md

@@ -470,3 +470,18 @@ Nothing.
 ## Ask
 
 None.
+
+**Postscript to the fifth tick — the count above said 50, and it is 51.**
+Committing `f59a592` left the very defect this lane keeps finding in documents:
+the docstring and the run said **50 cells** while `--selftest`'s argparse help
+string still said **42**, and nothing failed — caught by reading the blob back
+off the forge (`served-verify.py`, sha256 `4855de27…`, which matched the
+committed blob and still carried the stale line). `81d2c0a` closes it two ways:
+the help string no longer carries a number, and **cell 27** parses the
+docstring's `fixture corpus, N cells` claim and grades it against the count that
+actually ran. Measured RED (`before/cell27-red.txt`): a copy differing only in
+that claim prints `selftest: 51 cells, 50 passed, 1 failed` /
+`FAIL 27 … got: 50 want: 51`, **rc 1**. Selftest **51/51 rc 0**; gate at
+`81d2c0a` **5 of 5 legs PASS, rc 0** in the main tree, and **5 of 5 rc 0** in a
+fresh clone's linked worktree (all legs, `selftest-sweep` 15 tools / 15 OK /
+0 fatal). Both commits are pushed to `origin/main`.