Run 11 landing evidence, final fill: the post-push readback measured rather than promised -- the fill landed as 00df4e6, the same anonymous raw path re-read the check-in at HTTP 200 / 103,128 B, cmp byte-identical to disk, sha256 4a17e8ee17a65dce20898ae16e562a8aea22490ef31c40c3e8d8467c2bb6479e reproducing from git cat-file -p 00df4e6, so served/disk/committed agree on three sides at the revision that now exists and the pre-append row stands at 57895b2 (100,376 B / 87c275a1)

checkins/2026-10-12-merlin.md

@@ -1529,6 +1529,16 @@ reader can verify from the repository; the fill below lands as its own commit,
 and that revision is readable over the same path by the same script. Nothing
 else in the table moves.
 
+**Post-push verification of this fill, measured rather than promised.** The fill
+landed as `00df4e6`, and after that push the same anonymous raw path was re-read:
+`checkins/2026-10-12-merlin.md` → **HTTP 200 / 103,128 B**, `cmp` **byte-identical
+to disk**, and its sha256 `4a17e8ee17a65dce20898ae16e562a8aea22490ef31c40c3e8d8467c2bb6479e`
+reproduces exactly from `git cat-file -p 00df4e6:checkins/2026-10-12-merlin.md`
+(103,128 B) — so the served bytes, the disk bytes and the committed bytes agree on
+all three sides at the revision that now exists, and the pre-append row above is
+verifiable independently at `57895b2` (100,376 B / `87c275a1…`). The other two
+files are untouched by this fill and their rows above stand.
+
 Re-measured after the push, from this host: the live snapshot
 `/root/.helm/data/snapshot.json` is **14,039 B / sha256
 `aa842b0fd88037f83115b4a54d617f27666f4de06ef84f9a64c8fd0a5f04656d` / mtime_ns