Q34: landing evidence appended to the check-in (readback table: helm-null-gate.md 200/9924 sha 84b1e714, WORK-QUEUE.md 200/521480 sha 602746a5, check-in 200/6442 sha 08afa919, all cmp byte-identical over the anonymous raw path; live snapshot aa842b0f/14039/mtime_ns 1791479579475780303 delta 0; deployed bin untouched ee0b36a8/7ed1bca8/5c67473d; nothing deployed, the §4 cp is a three-file ask now)

checkins/2026-10-12-merlin.md

@@ -97,6 +97,22 @@ whether that pin should exist at all.
 
 Landing evidence, appended after commit and read back over the anonymous raw path
 (`https://forge.alexanderwhitestone.com/git/stackchain/troupe-standup/raw/branch/main/<path>`), no
-credential — each **HTTP 200** and `cmp` **byte-identical** to disk. Table filled at push time.
+credential — each **HTTP 200** and `cmp` **byte-identical** to disk:
+
+| file | status / bytes | sha256 |
+|---|---|---|
+| `recoveries/helm-null-gate.md` | 200 / 9,924 | `84b1e714bfad1c0be948845f0f0a9f92a739ce5b64b68a197523bbb7c0808a58` |
+| `WORK-QUEUE.md` | 200 / 521,480 | `602746a5f202cdc39c9d53f59af814e8ab8d0fd8930a0042c47c258ddc1a0aa0` |
+| `checkins/2026-10-12-merlin.md` | 200 / 6,442 (pre-append revision, as pushed in `a16d9e4`) | `08afa9193238bd68c06a2d54dccdd9659ba9601a8164edb06126d008d57822db` |
+
+Re-verified in the same breath, from this host: the live snapshot
+`/root/.helm/data/snapshot.json` is **14,039 B / sha256
+`aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d` / mtime_ns
+`1791479579475780303`** — delta 0 across the whole run after the restore. The deployed
+`/root/.helm/bin/helm-collect.py` is unchanged at `ee0b36a82f23fcf3…`, `helm-selftest.py` at
+`7ed1bca8f9da624f…` and `helm-render.py` at `5c67473d89283c3d…` — nothing deployed, the §4 `cp`
+remains Alexander's. `decisions/` and `inbox/` were not touched; no another-party file was edited;
+no secret is printed in this check-in or in the files it lands — the long strings are gate check
+names, snapshot JSON keys, file paths and sha256 digests.
 
 — Merlin