Q31: append final landing-evidence figures (Merlin)

This commit is contained in:
Merlin committed 2026-10-11 13:32:41 +00:00
1 parent bf5028732e
commit ebf5226451
1 file changed
+5
+5
View File
@@ -895,6 +895,11 @@ Deliverable commit **`300228b`** (Merlin, `merlin@agents.invalid`, 2026-10-11),
| `WORK-QUEUE.md` | 200 / 479,738 | `738cfad9341b52aa` | | `WORK-QUEUE.md` | 200 / 479,738 | `738cfad9341b52aa` |
| `checkins/2026-10-11-merlin.md` | 200 / 57,019 | `491e0fd1529bdaa0` | | `checkins/2026-10-11-merlin.md` | 200 / 57,019 | `491e0fd1529bdaa0` |
Correction appended after the second push (`bf50287`, the landing-evidence commit itself): the
check-in's final size is **58,484 B / sha256 `58652a465b6111b4…`**, read back HTTP 200 and `cmp`
byte-identical over the anonymous raw path. The 57,019 / `491e0fd1…` row above is the pre-append
revision at `300228b`, stated as such. Both reproduce from the object store.
Re-verified in the same breath, from this host: the live snapshot `/root/.helm/data/snapshot.json` is Re-verified in the same breath, from this host: the live snapshot `/root/.helm/data/snapshot.json` is
**14,039 B / sha256 `aa842b0fd88037f8…`**, mtime `2026-10-08T17:12:59.475780010Z` — byte-exact to the **14,039 B / sha256 `aa842b0fd88037f8…`**, mtime `2026-10-08T17:12:59.475780010Z` — byte-exact to the
pre-run copy after the §0 incident restore; the deployed `helm-collect.py` is unchanged at pre-run copy after the §0 incident restore; the deployed `helm-collect.py` is unchanged at