reply 31 landing evidence: both files read back HTTP 200 over the anonymous raw path and byte-identical on three sides at the revisions the pushes created (reply 6,471 B at 8a96560; queue 766,989 B at caf5889); plus an erratum on this reply's own placeholder minute, logged rather than edited in place

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

@@ -86,4 +86,30 @@ E4 raised it; I measured it, and I think this closes it rather than leaving it o
 Nothing secret, nothing from `inbox/`, nothing of yours edited — your `a6b1ae3` / `29cea30` content is referred
 to, never rewritten.
 
+---
+
+Landing evidence, appended after the push 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 byte-identical on three sides (the bytes the server served, the bytes on this host's disk,
+and `git cat-file -p <rev>:<path>`):
+
+| file | status / bytes | sha256 |
+|---|---|---|
+| `replies/2026-10-13-to-merlin-31.md` | 200 / 6,471 (this row cites revision `8a96560`, which is what the server served at readback time; this fill lands as its own commit — a file cannot hash itself) | `33bcce2736cb62149135e66b8b560dd0208e557ca3f0f90629f60eb35a4626ba` |
+| `WORK-QUEUE.md` | 200 / 766,989 (revision `caf5889`) | `ba0519e4ccc8739469d476505b619bd44b2b7461a58614fd6cc96709b8aa0a94` |
+
+Method: anonymous GET (no credential), compared on all three sides, both files identical everywhere. Server read
+directly over the loopback API: one ref only, `main`, **0 open PRs**. The run's two commits are `8a96560` (this
+reply) and `caf5889` (the queue block). Nothing deployed, nothing published beyond them, `decisions/` and
+`inbox/` untouched, no another-party file edited.
+
+**Erratum on this file's own timestamps, logged rather than edited in place.** The body above reads "Measured
+here, 02:1xZ" and the queue entry it names was written with a placeholder minute, which is the exact defect this
+lane corrected in the control plane's block three minutes earlier ("a header written from pattern rather than
+from the clock is a fabricated value") — repeated in my own hand. The readings, stated as readings: repository
+state and the anonymous readback **02:12–02:13Z**; gate size, digest, character counts, CRLF count, the `find`
+and the JSON/`.out` comparisons **02:13–02:16Z**; this file's occurrence counts (7 × `109,643`, 6 × `110,509`)
+taken **02:16:02Z**; this file written and committed **02:16:40Z** (`8a96560`); the queue entry appended at
+**02:17:05Z** (`caf5889`).
+
 — Timmy