landing evidence for Q29 (cf3547c): anonymous raw readback, 200 + cmp-identical on all three files
This commit is contained in:
1 parent
cf3547cd1a
commit
1a58ae487d
1 file changed
+22
@@ -530,3 +530,25 @@ Read back over the anonymous raw path (`…/raw/branch/main/<path>`), no credent
|
||||
HTTP 200 and `cmp` byte-identical to disk. Table appended after the push below.
|
||||
|
||||
— Merlin
|
||||
|
||||
Deliverable commit **`cf3547c`** (Merlin, `merlin@agents.invalid`, 2026-10-11; parent `9928a62`),
|
||||
3 files, pushed to `origin/main` (`git log --oneline -1 origin/main` → `cf3547c`). Read back over
|
||||
the anonymous raw path (`…/raw/branch/main/<path>`), no credential — each HTTP 200 and `cmp`
|
||||
byte-identical to disk:
|
||||
|
||||
| file | status / bytes | sha256 (first 16) |
|
||||
|---|---|---|
|
||||
| `recoveries/render-site-guards.md` | 200 / 16,728 | `906753079a020c14` |
|
||||
| `WORK-QUEUE.md` | 200 / 432,307 | `8dd98ff72155f960` |
|
||||
| `checkins/2026-10-11-merlin.md` | 200 / 34,351 | `9748ad482153c0c6` |
|
||||
|
||||
Re-verified in the same breath: the shared build tree's `build_blocks.py` is still sha256
|
||||
`97fedb5dd5e85d2…`, `blocks.json` `63c9cee6103a6824…`, `find /root/stackchain-legends-build
|
||||
-newermt '2026-10-11 04:00' -type f` returns nothing, and the live ledger index
|
||||
`https://alexanderwhitestone.com/stackchain/blocks/` is 200 / 34,488 B /
|
||||
`4f764ef4dfb9c08b2654ff0783550d20ad1bb7a31cb0c32070974a5fe451557e`. `blocks.json` was read-only
|
||||
throughout; `decisions/` and `inbox/` were not touched and nothing was executed. The patched
|
||||
builder `c4127c6c…` is scratch-local in `/root/crucible/q29/` and stays there — publishing it is
|
||||
Alexander's, the same gate Q26/Q13/Q27/Q28 state. No secret is printed in this check-in or in the
|
||||
files it lands; the long strings in them are archive prose, build-failure messages, HTML fragments
|
||||
and sha256 digests.
|
||||
Reference in new issue
Block a user