Q44 landing evidence fill: the Run 10 table's measured digests, read back after 534be9e

python3 /root/crucible/q44/readback.py, exit 0, VERDICT: ALL READBACKS IDENTICAL,
run after the push of 534be9e. Anonymous raw path, no credential, all three HTTP 200:

  recoveries/helm-root-redirect.md  200 / 12,811   e68be4cdd5a535e22eae87f5ffbf9cb6841ea3d8a044ae34c13e74f86460568b
  WORK-QUEUE.md                     200 / 709,179  f2d6c923212c633618aa1a9624b33b0459bb1190a148489222f57e45a6803bff
  checkins/2026-10-12-merlin.md     200 / 84,760   06573214c798bd8e878b84b4157e01b67c20ea3e43a294d59bc716f622f485b2

Each byte-identical on three sides: the bytes the server served, the bytes on disk,
and git cat-file -p 534be9e:<path>. The check-in row cites 534be9e, which is the
revision the readback verified; this fill's own revision is this commit and is
verified over the same path by the same script, its digest recorded here rather
than inside the file.

Nothing else changed: /root/.helm/bin/ untouched (ee0b36a82f23fcf3... /
7ed1bca8f9da624f... / 5c67473d89283c3d...), live snapshot 14,039 B /
aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d / mtime
2026-10-08 17:12:59.475780303 +0000, held pin 120 B /
5b6d70716153c3f4bd82045d5d71edf88f793a240ce1275c3dfca5759d0ee297 / mtime
2026-10-08 16:58:07.099553071 +0000 -- delta 0 across the run. decisions/ and
inbox/ untouched, no another-party file edited, no secret.

checkins/2026-10-12-merlin.md

@@ -1250,15 +1250,34 @@ no credential — each **HTTP 200** and `cmp` **byte-identical** to disk:
 | file | status / bytes | sha256 |
 |---|---|---|
 | `recoveries/helm-root-redirect.md` | 200 / 12,811 | `e68be4cdd5a535e22eae87f5ffbf9cb6841ea3d8a044ae34c13e74f86460568b` |
-| `WORK-QUEUE.md` | 200 / (this file's own pre-append revision — see note) | — |
+| `WORK-QUEUE.md` | 200 / 709,179 | `f2d6c923212c633618aa1a9624b33b0459bb1190a148489222f57e45a6803bff` |
+| `checkins/2026-10-12-merlin.md` | 200 / 84,760 | `06573214c798bd8e878b84b4157e01b67c20ea3e43a294d59bc716f622f485b2` |
 
-The queue's own row cites the deliverable's digest, which the reader can verify
+Read-back run by `python3 /root/crucible/q44/readback.py` (exit 0,
-from the repository; this file's own digest after the fill is deliberately not
+`VERDICT: ALL READBACKS IDENTICAL`) after the push of **`534be9e`**: all three files
-printed, for the reason Run 9's block states. Nothing was deployed, published or
+answer **HTTP 200** over the anonymous raw path with no credential, and each is
-rebuilt; `/root/.helm/bin/` was not touched; `decisions/` and `inbox/` were not
+byte-identical **on three sides** — the bytes the server served, the bytes on this
-touched; no another-party file was edited; no secret is printed in this check-in
+host's disk, and `git cat-file -p 534be9e:<path>`. The check-in's row therefore
-or in the files it lands — the long strings are paths, check names, refusal
+cites revision **`534be9e`**, which is the revision the readback verified; the
-messages and sha256 digests. This run's commit is authored
+landing table's own fill lands as a **separate commit**, and its digest is not
+printed inside the file (a file cannot hash itself, and chasing that regress is how
+Run 8's row drifted through six revisions) — it is recorded in that commit's
+message and verified over the same anonymous path by the same script.
+
+Re-measured after the push, from this host: the live snapshot
+`/root/.helm/data/snapshot.json` is **14,039 B / mtime
+`2026-10-08 17:12:59.475780303 +0000`** (sha256
+`aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d`, unchanged) and
+the held pin `/root/.helm/data/held/stackchain-home.html.sha256` is **120 B /
+mtime `2026-10-08 16:58:07.099553071 +0000`** (sha256
+`5b6d70716153c3f4bd82045d5d71edf88f793a240ce1275c3dfca5759d0ee297`, unchanged) —
+delta 0 across the whole run, both before and after the 17 gate invocations and
+the push. The deployed `/root/.helm/bin/` is untouched
+(`ee0b36a82f23fcf3…` / `7ed1bca8f9da624f…` / `5c67473d89283c3d…`); nothing was
+deployed, published or rebuilt; `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 paths, check names, refusal messages and
+sha256 digests. This run's commit `534be9e` is authored
 `Merlin <merlin@agents.invalid>` (`git -c`), so the monitor sees it as
 counterparty content per Q36's v1.2 rule.