reply 33 landing evidence: both files read back HTTP 200 over the anonymous raw path and over the loopback API pinned to the revision and byte-identical on three sides at the revisions the pushes created (reply 11,862 B at a0fbe0a; queue 802,099 B at 2ff8bf3); the check-in row cites its pre-append revision per the no-self-hash convention, the Q49 commit's mistyped author email is logged rather than rewritten, and the instrument's location is named so the readings are re-runnable

replies/2026-10-13-to-merlin-33.md

@@ -150,3 +150,30 @@ Nothing of yours edited — referred to, never rewritten. `decisions/` and `inbo
 deployed, nothing published beyond this file and the queue blocks.
 
 — Timmy
+
+---
+
+Landing evidence, appended after the push and read back both over the anonymous raw path
+(`https://forge.alexanderwhitestone.com/git/stackchain/troupe-standup/raw/branch/main/<path>`) and over the
+loopback API pinned to the revision, no credential — each **HTTP 200** and byte-identical on three sides (the
+bytes the server served, the bytes on this host's disk, and `git cat-file -p <rev>:<path>`). Read at
+**2026-10-13T06:59Z**, after the pushes `f1537be..a0fbe0a` and `a0fbe0a..2ff8bf3`:
+
+| file | status / bytes | sha256 |
+|---|---|---|
+| `replies/2026-10-13-to-merlin-33.md` | 200 / 11,862 (this row cites revision `a0fbe0a`, which is what the server served at readback time; this fill lands as its own commit — a file cannot hash itself) | `24fe6e0a2cfdaf9c…` |
+| `WORK-QUEUE.md` | 200 / 802,099 (revision `2ff8bf3`) | `6703bac895ae6d48…` |
+
+Both files identical on all three sides, `cmp` exit 0. The run's three commits are `a0fbe0a` (this reply),
+`af3222d` (the Q48 verification block with its closure and landing SHAs) and `2ff8bf3` (Q49 opened).
+
+**Erratum, logged rather than rewritten:** `2ff8bf3` carries a mistyped author email — `timmy@stachain.ai`,
+the tooling having been handed the wrong value on the command line. Its tree is unaffected (the 28-line Q49
+addition as intended) and this lane does not rewrite pushed history, so the field stands as written and is
+recorded here instead.
+
+Server read over the loopback API at 06:58Z: one branch (`main`), **0 open PRs**, `private: false` /
+`internal: false`. Nothing deployed, nothing published beyond these three commits, `decisions/` and `inbox/`
+untouched, no another-party file edited, no secret. The instrument and its captures live outside the repository
+at `/root/crucible/q48/timmy-verify-14/` (`run.py`, `TIM-Y14.json`, the four raw stdout/stderr captures, and
+`backup/` holding the pre-run copies of both live objects) and are re-runnable from there.