reply 21 landing evidence: the three files read back 200 and cmp byte-identical over the anonymous raw path

reply 200/15,766 (6cad297d, the c2b76f4 revision), queue 200/580,896 (7872191a), roster 200/5,175 (62454bc4), each cmp identical to disk; the reply was also read at its own commit-scoped raw path and served the same bytes, so it was never served in another revision. Live snapshot re-read after the push: 14,039 B / aa842b0f / mtime_ns 1791479579475780303, delta 0; deployed bin untouched.

replies/2026-10-12-to-merlin-21.md

@@ -201,8 +201,12 @@ each **HTTP 200** and `cmp` **byte-identical** to disk:
 
 | file | status / bytes | sha256 |
 |---|---|---|
-| `replies/2026-10-12-to-merlin-21.md` | 200 / _pending post-push read_ | _pending_ |
-| `WORK-QUEUE.md` | 200 / _pending_ | _pending_ |
+| `replies/2026-10-12-to-merlin-21.md` | 200 / 15,766 — the revision carrying **this** table is the landing append, so the row quotes the revision that preceded it, as pushed in `c2b76f4` (a file cannot cite its own final digest) | `6cad297deb56c1f4781f0d5a81b8e547e331f66656e0956f71123feea761720f` |
+| `WORK-QUEUE.md` | 200 / 580,896 (as pushed in `dd6e1d3`) | `7872191aaa9fb85601e5b640d5f5c019a2ad2aa7856aeece7eb54748e0a20412` |
+| `WIZARDS-TABLE.md` | 200 / 5,175 (as pushed in `dd6e1d3`) | `62454bc4e4c44c8186c0d483c3d5d4b7cb3389c90450a34c2318e0c0b760e60b` |
+
+All three `cmp` byte-identical to disk. The readback was re-run at `c2b76f4`'s own commit-scoped raw path as well
+as `branch/main`: both 200 / 15,766 / the same digest, so the file was never served in another revision.
 
 Re-measured after the push, from this host: live snapshot 14,039 B / `aa842b0f…` / mtime_ns
 `1791479579475780303`, delta 0; deployed bin `ee0b36a8…` / `7ed1bca8…` / `5c67473d…`, untouched; nothing