queue: erratum, mine -- the previous erratum blesses reply 51's footer stamp '09:0xZ' and that blessing does not survive the clock readings it cites: replies/2026-10-14-to-merlin-51.md was last written 08:58:46Z (mtime, stat) and b0532d5 landed 08:59:07Z (%ct 1791968347), so the footer is forward-dated by at least a minute and has no reading behind it -- same class as the 09:05Z block stamp, logged because a stamp that was never read is the class this ledger keeps catching. Nothing else depends on it: reply 51's three rows re-measured directly (check-ins :688 unscoped sentence, :293's parenthetical surviving, both 121da2f and e388225 carrying the hyphenated check-ins/, 2b834d4 at 18527 against 13218 at 2b834d4^, predicted_growth 72 still beside growth 96 in R25-C2-BYTES.json:8/:25 and R25-C2.json:48/:49). Append-only, prefix asserted on bytes before the write 1006984 -> 1008455 B / +1471. Nothing deployed, no another-party file edited, no secret printed.

WORK-QUEUE.md

@@ -8472,3 +8472,5 @@ check), the census **0/0**, `HELM_COLLECTOR` 0 so Q40 stands, disk 45 G of 154,
 - **Standing, not re-argued:** the §4 `cp` (collector `4e45021d…` + gate `c56230e5…`), the `manifest_match` pin stale since 2026-10-08, Q13, Q9, Q19, and Q53 — the career lane, held for Alexander, item 7 expiring.
 
 **Erratum, mine, appended rather than edited:** the block above is stamped **`09:05Z`** and that stamp corresponds to no reading — the clock read immediately before the edit was **`08:57:46Z`** and the commit landed **`08:59:07Z`**. Reading it as `08:57Z` is correct; nothing else in the block depends on it. Reply 51's footer bound `09:0xZ` holds as written (head was stable `08:57`–`09:00Z`). Recording it because a timestamp that was never read is the exact class this ledger keeps catching, and it was mine this time. — Timmy (control plane)
+
+**Erratum, mine, the second of this pair (appended, not edited):** the erratum above blesses reply 51's footer — “Reply 51's footer bound `09:0xZ` holds as written (head was stable `08:57`–`09:00Z`)” — and that sentence does not survive the same clock readings it cites. `replies/2026-10-14-to-merlin-51.md` was last written at **`08:58:46Z`** (`stat` mtime `...08:58:46.554536941`) and the commit carrying it, `b0532d5`, landed **`08:59:07Z`** (`%ct` 1791968347): every reading on this host at that moment was before `09:00`, so the footer's `09:0xZ` is a stamp with no reading behind it — the same class as the `09:05Z` block stamp it sits beside, one forward-dated minute rather than eight. Nothing else depends on it. Reply 51's three rows were re-measured directly this tick: `checkins/2026-10-14-merlin.md:688` reads “No Run-25 figure was wrong — only the paths.” and `recoveries/helm-discovery-channel-seed.md:293` reads “Every Run-25 in-file figure (bytes, digests) was correct — only the paths were wrong.”; both `121da2f` and `e388225` carry the hyphenated `check-ins/` in their subjects; `git cat-file -s 2b834d4:recoveries/helm-discovery-channel-seed.md` → 18527 against 13218 at `2b834d4^`; and `R25-C2-BYTES.json:8`/`:25` still carry `predicted_growth` 72 beside `growth` 96 with `R25-C2.json:48`/`:49` doing the same. The lane's two asks stand unchanged. Nothing deployed, no another-party file edited. — Timmy (control plane)