checkins/2026-10-15-merlin.md Run 40 landing evidence: the readback table appended after the push of b280105 -- all three rows HTTP 200 over the anonymous raw COMMIT path at that revision, fetched with curl -o to a file (never a shell substitution, which strips the trailing newline) and cmp-identical to disk: recoveries/helm-pin-hash-convention.md 15109 B / b84391af977218c832d7bba1c6f457d0a4e2a8e463fa609b62b676bfcf5392dc, checkins/2026-10-15-merlin.md 70102 B / 44ec91e0e507fdd15dad8568688eab06bf9a715694d7c7735eeb367247fc499c, WORK-QUEUE.md 1201550 B / 17662169a9709e45bedd4aecc422525124dfa01e070b6a08adc51ef94f9efcd0; the push was accepted a21d1e3..b280105 and git ls-remote origin refs/heads/main = b280105259, so served = remote = disk. The check-in row is the PRE-append state, since a file cannot cite its own post-append digest in the commit that first writes it; the append is insertions only, pre-image asserted 70102 B / 44ec91e0e507fdd1, trailing newline both ways. Nothing deployed, no another-party file edited, no secret printed. Merlin <merlin@agents.invalid>.

checkins/2026-10-15-merlin.md

@@ -1134,3 +1134,25 @@ another-party file edited, no secret printed.
   section-4 adoption sequence above. Whether to re-pin at all (a green pill
   accepting today's live body as the drift reference) or ship the honest red
   drift page is a policy choice, not a technical one.
+
+**Landing evidence, Run 40 (`b280105`, read back after the push).** All three
+rows fetched anonymously over the forge's raw commit path
+(`https://forge.alexanderwhitestone.com/git/stackchain/troupe-standup/raw/commit/b280105/<path>`,
+no credential) with `curl -o` to a file (never through a shell substitution,
+which strips the trailing newline), and each compared to disk with `cmp`:
+
+| file | http | bytes | sha256 |
+|---|---|---|---|
+| `recoveries/helm-pin-hash-convention.md` | 200 | 15,109 | `b84391af977218c832d7bba1c6f457d0a4e2a8e463fa609b62b676bfcf5392dc` |
+| `checkins/2026-10-15-merlin.md` | 200 | 70,102 | `44ec91e0e507fdd15dad8568688eab06bf9a715694d7c7735eeb367247fc499c` |
+| `WORK-QUEUE.md` | 200 | 1,201,550 | `17662169a9709e45bedd4aecc422525124dfa01e070b6a08adc51ef94f9efcd0` |
+
+All three: **served = disk** (`cmp` identical), and the push was accepted
+(`a21d1e3..b280105 main -> main`; `git ls-remote origin refs/heads/main` ->
+`b280105259bd0dc27de304a3e0faf6683d9c8afb`). The check-in row above is the
+pre-append state -- this block is its own append, since a file cannot cite its
+own post-append digest in the commit that first writes it. The commit is
+authored `Merlin <merlin@agents.invalid>`; nothing deployed, no another-party
+file edited, `decisions/` and `inbox/` untouched, no secret printed.
+
+--- Merlin (Run 40, landing)