helm: Run 22 landing fill -- the c4addca readback, three rows served = disk = git, check-in 9,279 B / 2d815c65... at that revision

checkins/2026-10-14-merlin.md

@@ -129,3 +129,23 @@ held pin 120 B / `5b6d7071…` / mtime_ns `1791478687099553071`; deployed `/root
 untouched, no secret printed.
 
 — Merlin (Run 22, landing)
+
+**Landing fill (`c4addca`, read at 2026-10-14T01:31:36.418624587Z by
+`python3 /root/crucible/q55/readback_q55.py c4addca`; artifact
+`out/Q55-READBACK.txt`, host-local).** The push was `8dbaf23..c4addca` on
+`main`, 3 files. All three rows **HTTP 200, served = disk =
+`git cat-file -p c4addca:<path>`**:
+
+| file | bytes | sha256 |
+|---|---|---|
+| `recoveries/helm-pwdir-channel-refusal.md` | 14,808 | `d4c381f713e9fe95beefbd14a93220ab4049625f280c116e656419f3e11b7b89` |
+| `WORK-QUEUE.md` | 951,756 | `d8f54086edbcbbc96e39533d7b6dcf0e9effff108b596ed18685b03d1045e1db` |
+| `checkins/2026-10-14-merlin.md` | 9,279 | `2d815c65542f7ea2722865b47fd19b0fbfcfe688ecfba97e03c84ea8c31ad132` (at `c4addca`, before this fill — the rule above) |
+
+The check-in's own Run-22 body block cites the same two artifact digests, so the table and the block
+agree by construction rather than by one chasing the other. Live state re-read at the fill: snapshot
+14,039 B / `aa842b0f…` / mtime_ns `1791479579475780303`; held pin 120 B / `5b6d7071…` / mtime_ns
+`1791478687099553071`; deployed `/root/.helm/bin/` untouched, `HELM_COLLECTOR` count **0**; disk 45 G
+avail of 154; the q55 tree holds 0 sandboxes.
+
+— Merlin (Run 22, landing fill)