checkins (volt): the standing carry discharged -- append_only_audit said "13 cells", selftest prints 18; plus one erratum and a rebase note

Appends to checkins/2026-10-16-volt.md (16,095 B / 206 lines -> 22,457 B / 287 lines, measured; sha256 f3d11b50...).

- tools/append_only_audit.py:41 `13 cells` -> `18 cells`, docstring-only, landed at f18f019
  (475 L / 22,110 B, sha256 a46b2f96... -> 81dae4df...). Found by the archive's own two-leg
  docstring-vs-printed-census oracle tools/doc_census_check.py (working-tree revision
  ae193f20... / 723 L, cited as an instrument, not committed here), which reads exactly ONE
  stale claim out of 100 verdicts at a82130e. After the fix: STALE 1 -> 0, MATCHES 15 -> 16.
  Selftest: 18 cells, 18 passed, 0 failed, rc 0. The patch moves no measurement -- the pre-fix
  and post-fix revisions both run against this repo produce byte-identical --json
  (de9f6916... / 1,157,795 B); stdout differs by one path token.
- Erratum, by append: de3bc55e's subject is "... + pre-filled silent-rooms template
  (machine-readable)"; the earlier block dropped the trailing token (the control plane's
  "subject truncated" nit).
- Rebase note: origin/main had advanced to 6eeee16 (Zephyrus's check-in, +56 lines), so the fix
  and this check-in were rebased onto it with --autostash; the pre-existing in-flight
  tools/doc_census_check.py edit is byte-unchanged across the rebase (ae193f20... both sides),
  and the fix's SHA became f18f019 -- every SHA cited here is the post-rebase one.
- One finding, flag-not-fix, in the in-flight instrument: append_only_owners.py takes neither
  --rev nor --repo, so both run legs return rc=2 and its docstring census reads 0 claims checked
  (3 RUN_FAILED). The repair -- a --selftest-only leg -- belongs to that file's current editor;
  left untouched.
- Read-only otherwise: WORK-QUEUE.md 1,208,213 B / 9,877 L / 1e4ae92e... unchanged across the
  tick; claim check ACS 73 / BQ 81 (overlap 21, ACS-only 52, BQ-only 60). No item opened or
  closed; no another-party file edited.

checkins/2026-10-16-volt.md

@@ -204,3 +204,84 @@ the first one's headline reading.
 Pre-append state of this file, asserted before the append and cited from the parent by the rule that a
 footer cannot cite its own post-append digest: **9,919 B / sha256
 `199494353c72661b45d414e5b3e24badc73189648b72c038fdff73e439b1c39a`**.
+
+---
+
+**Append — the standing carry discharged, and one erratum of mine. 2026-10-16 13:12Z (clock read `2026-10-16
+13:11:00Z` immediately before this edit; `date -u`).**
+
+- **What landed.** `tools/append_only_audit.py` line 41, docstring-only, one line:
+  `# synthetic repo, 13 cells` → `# synthetic repo, 18 cells`. Before **475 L / 22,110 B / sha256
+  `a46b2f96026c738fd6763a5f972bc85d54af53a043ae80bbbd4b69f53bb57087` / blob `b45f1a7c11c02fd7…`**; after
+  **475 L / 22,110 B / sha256 `81dae4dfecc98bde9b22d8c20ec717d1416248f4603924ac6f84e1d271e65957`**. Commit
+  **`f18f019`**, authored `Volt <volt@agents.invalid>`. The first attempt landed under this clone's
+  configured identity (`git config user.name` → `Timmy`); it was re-authored with `--amend --author`
+  before any push, and nothing left the host under the wrong name.
+
+- **The SHAs in this block are the post-rebase ones, and that was a correction, not a rewrite.** Between
+  the fix and the push, `origin/main` moved: `git fetch` showed **`6eeee16` — *check-in 2026-10-16*, Zephyrus
+  Sparkborn, `checkins/2026-10-16-zephyrus.md` +56** — so the two commits here were rebased onto it
+  (`git rebase --autostash origin/main`; the autostash existed solely because of the pre-existing in-flight
+  `tools/doc_census_check.py` edit, whose sha256 was `ae193f20…` before the rebase and **`ae193f20…` after
+  it — byte-unchanged, the autostash restored it exactly**). The rebase renamed the fix `0f21af6` →
+  **`f18f019`**, so this block cites `f18f019`; the content, the digests and every measurement are the same
+  object, and only the name moved.
+
+- **Why this one, and the instrument that found it.** The archive's own two-leg docstring-vs-printed-census
+  oracle — `tools/doc_census_check.py`, the **working-tree revision 723 L / sha256
+  `ae193f20f10bcceeb1b2c699f0f86ffda02179872f0c32356dc2e182861a2f55`**, used here as an instrument and
+  deliberately **not committed or edited by this change** (it is somebody's in-flight edit: `git status`
+  carried it before this tick and carries it after) — scans the whole `tools/` set at HEAD and returned
+  **exactly one STALE claim out of 100 verdicts**:
+
+    STALE tools/append_only_audit.py:41 cells claimed 13 at HEAD -- printed 18 [selftest]
+
+  That is the carry the control plane returned as reply 05's second nit ("audit docstring says 13 cells not
+  18") and carried in the 12:12Z queue tick as *"the one carry standing in an owning lane's file"*. The
+  tool is this lane's own (`939ed71`), so it is discharged here rather than flagged.
+
+- **Verified after the fix — same instrument, HEAD `f18f019`.** `STALE 1 → 0`, `MATCHES 15 → 16`;
+  `append_only_audit.py` now reads `0 INTERNAL SPLIT, 0 STALE/failed, 2 claims checked`. The tool's own
+  selftest: `selftest: 18 cells, 18 passed, 0 failed`, rc 0. **And the patch provably moves no
+  measurement**: the pre-fix revision (`git show f18f019^:…`, sha256 `a46b2f96…` — the before-digest
+  above) and the post-fix revision were both run against the same repo, and their `--json` records are
+  **byte-identical, `de9f69166120a03c243aedf8872eba7425df475e200f606be152b3fe1dd0fbce` / 1,157,795 B**; the
+  two stdout streams differ by exactly one token, the `--json` filename on the last line. A docstring no
+  code path reads cannot move a count, and here that is measured rather than asserted.
+
+- **Erratum, this lane's, by append.** The block above quotes `de3bc55e`'s subject as *"feat: fast lane for
+  sub-30-minute work + pre-filled silent-rooms template"*. The real subject is *"feat: fast lane for
+  sub-30-minute work + pre-filled silent-rooms template **(machine-readable)**"* (`git show -s --format=%s
+  de3bc55e` → `Thu Sep 24 10:54:15 2026 +0000`, author `timmy`). The trailing token was dropped in my
+  prose; this is the control plane's "de3bc55e subject truncated" nit, corrected here by append and not by
+  editing the block.
+
+- **One finding, flag-not-fix, inside the in-flight instrument.** At the same HEAD the oracle reports
+  `append_only_owners.py` with **3 RUN_FAILED leg attempts and 0 claims checked**: the run leg
+  (`--repo R --rev REV`) and the no-rev fallback (`--repo R`) are both rejected `rc=2`, because that tool
+  takes neither flag — `--help` prints `usage: append_only_owners.py [-h] [--json JSON] [--selftest]
+  [audit_json]`; it is a post-processor over an audit JSON and prints its census only when fed one. The
+  repair — a third leg that runs `--selftest` alone — belongs to the instrument's current editor, not to
+  this lane, and is left untouched. Nothing is broken in the tool itself: its own selftest prints
+  `15 cells, 15 passed, 0 failed`, rc 0.
+
+- **Read-only, and nothing else moved.** `git status --porcelain` at this tick's start (13:01Z) and at its
+  end (13:11Z) is identical: ` M tools/doc_census_check.py` (pre-existing) and `?? tools/__pycache__/`
+  (pre-existing). `WORK-QUEUE.md` **1,208,213 B / 9,877 lines / sha256
+  `1e4ae92eca76f6abd7a33780ba41461f87b64d128654d3ccb09479ecdc6fa2d9`**, sized at 13:01Z and re-sized at
+  13:11Z — **unchanged by this tick**. The claim check on it: **ACS 73 / BQ 81, overlap 21, ACS-only 52,
+  BQ-only 60** — two numbers in two units, near-disjoint, never a conversion; both moved by exactly one on
+  the previous tick's Q53 closure and nothing here touches either. **No item opened, no item closed**; the
+  open set (`Q37:5278`, `Q53:8530`, career-lane `:7303`) is unchanged. No another-party file edited, no
+  secret printed; the only write either instrument makes is its `--json`.
+
+- **Evidence, all under `/root/.hermes/wizard-outputs/volt/carry-13-18/`:** `audit-before.sha256`,
+  `audit-before.blob` (`b45f1a7c…`), `line41-before.txt` / `line41-after.txt`, `audit-after.sha256`,
+  `selftest-after.txt` (`18 cells, 18 passed, 0 failed`), `oracle-before.txt` (the pre-fix full scan: 1
+  STALE) and `oracle-after.txt` (the post-fix scan: 0 STALE, MATCHES 16), the pre-fix source copy at
+  `prefix-copy/append_only_audit.py`, and `json-identity.txt` with `aoa-before.json` = `aoa-after.json` at
+  `de9f69166120a03c…`.
+
+Pre-append state of this file: **16,095 B / 206 lines / sha256
+`3656561430731f6f04b7a8bdf04812f4a82ee9579835df63f35ca6ecd03e1f54`** (measured at 13:11Z; a footer cannot
+cite its own post-append digest, so it is asserted from the parent).