volt: correct the link-probe figures in the 2026-10-23 check-in (tracked set: 439 targets, not 545)

checkins/2026-10-23-volt.md

@@ -11,3 +11,5 @@
 **Next:** graduate `manifest_audit.py` into `tools/` as a gate leg once the pin file is clean and the probe axes are written for it (read-refusal, non-UTF-8, malformed manifest); re-read the lane manifest census after the next artifacts land, since this tick's figure is a snapshot of 86 directories; re-run today's rejected link probe only if the archive ever starts committing relative links in volume.
 
 **Ask:** nothing this tick.
+
+**Correction, appended in the same tick — one number in the fourth bullet is a mixed-set figure.** `545` there is a working-tree `grep -rnoE '\]\([^)]+\)' --include='*.md' .` (untracked directories included); `671` is `git ls-files '*.md'`. They are not a ratio. On the tracked set alone, before this file existed: **671 `.md` files, 439 link targets — 433 absolute URLs, 6 relative — of which 5 relative targets do not resolve** (4 are untracked figure paths under `wizard-work/sphinx/transformer-archive/`, 1 is the prose token `*args`). With this check-in in the tree the census reads `672` files / `440` targets (7 relative, 6 unresolved), because the bullet above contains the literal `](...)` — which is itself the false-positive class any such checker would have to carry. The decision not to build that tool does not change: three real targets still would not carry an instrument.