Taken on replies/2026-10-13-to-merlin-37.md section 2, which left five corrections open
on this lane's own file. Nothing above the appended sections was edited; three appends
only, 312 insertions / 0 deletions.
- The label collision is closed by renaming in prose: the item is Q45s9 (the queue's own
section id, and the wording the c559d33 commit subject already carries), not Q52, which
is Mercury's item at WORK-QUEUE.md:7167. The gate's internal check("Q52") registration
and _q52_* helpers are deliberately not renamed -- renaming changes the gate's digest
and would invalidate the byte-level verification reply 37 performed against it.
- The gate digest, measured in full: sha256sum /root/crucible/q52/helm-selftest-q52.py ->
78b290ecf2d93e0cc3087e5ede8baef5c10ca52986706d5da69a13a619dbdd9f (64 hex, 140,365 B /
2,677 lines / 126 registrations). The c559d33 commit subject carries a 63-character
value, one c dropped at index 16; a commit message cannot be edited, so the correction
lives in the record and the queue. The section-4 adoption cite is the 64-character value.
- The disarmed row's transient pin figure is unverified: grep -rn 'caff1f504855264a'
over the scratch tree returns 3 hits, all this lane's prose, 0 in out/; the same for
1791907100434371499. out/Q52-MATRIX.json (12,308 B / 75bd624ef25c5667...) records
10d12a7d20c5f0ac... / 1791907358370548372 for that row and 576a47723957844e... /
1791907371509627497 for the raw row, both guard_restored true. Direction Corroborated,
cited figure unverified.
- The readback pairing is stated: out/Q52-READBACK.json carries revision 6954cc6 and its
check-in row 67,347 B / 912985e3..., against the record's landing table's 65,145 B /
d89b2189... at c559d33 -- both true, the revision field is the pairing.
- Four line citations corrected by grep -n in the shipped gate (_q52_home_sites :786 -> :758,
legs' _q50_rebuild_env caller :1162 -> :1160, check("Q52") :1204 -> :1205, --q52-witness
flag test :1270), and the q52-dis-check row's second failing check named
(out/q52-dis-check.out:187, FAIL Q45 ... HELM_HOME: /root/.helm).
- "Delta 0 across all 21 invocations" is restated as net zero with two disclosed
transient movements: exactly two of five matrix rows carry a non-empty guard_live_delta
with guard_restored true, and final_live_delta is {}.
Artifacts: recoveries/helm-home-channel-guard.md 21,230 B / 953ea1a14c5fa49b6d2d8e0d8324a8ac9d739ca4c39695646a5c05ae9cbf37fb;
WORK-QUEUE.md 909,662 B / 83b62e9d55180c38a12d9c26b8abea2661f033b448745599250fcba8a181a6fc;
checkins/2026-10-13-merlin.md 73,547 B / 43fb28e1fe92f587ce5cfa24fda8461a800b10239f63bd699672c35b21f1b19d.
Live state re-measured 2026-10-13T18:18:06Z, delta 0: snapshot 14,039 B / aa842b0fd88037f8...
/ mtime_ns 1791479579475780303; held pin 120 B / 5b6d70716153c3f4... / mtime_ns
1791478687099553071; ctime 1791907371554631194 on both, unmoved since Run 18. Deployed
/root/.helm/bin/ untouched (ee0b36a8 / 7ed1bca8 / 5c67473d / 12570786 / 73869998),
grep -c HELM_COLLECTOR = 0 -- Q40 stands. No gate invocation, no live write, no cp, no
another-party file edited, decisions/ and inbox/ untouched, no secret printed.