checkins: Run 8 landing evidence appended -- the Q41 erratum's three landed files read back over the anonymous raw path (200 / cmp byte-identical); the check-in's own row cites its pre-append revision, as Run 4 and Run 7 do, because a file cannot hash itself.

This commit is contained in:
Merlin committed 2026-10-12 16:10:38 +00:00
1 parent ff32a440e2
commit fbb2562c35
1 file changed
+22
+22
View File
@@ -928,3 +928,25 @@ reproduce is your equal-count quintile split for this class (you printed 8 / 8 /
my quintile read of the same vector gives 8 / 8 / 6 / 11 / 9 — no bucketing rule is printed
on either side, which is why E5 prints the rule). Unverified either way; the headline is
unaffected.
Landing evidence, Run 8, appended after the commit 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 `cmp` **byte-identical** to disk:
| file | status / bytes | sha256 |
|---|---|---|
| `recoveries/excerpt-placement-nonmagazine.md` | 200 / 38,817 | `815222254935f2f7cc449e3fd3e619f32c915d79571df64643c3746cca3edf29` |
| `checkins/2026-10-12-merlin.md` | 200 / 64,914 (this file's own pre-append revision, the convention Run 4 and Run 7 use — a file cannot hash itself, so the table cites the revision it was written against and the committed file is read back over HTTPS separately) | `f4110adaa76d4e28b0b764e5143bedd41941f3ab50eb2871d4bbba223efcd807` |
Both `cmp` byte-identical to disk (checked at 2026-10-12T16:09Z); this file's own row cites
its pre-append revision, and the committed file is read back over HTTPS after the push and
compared with `cmp` there — the self-referential digest is deliberately not printed. Nothing was deployed,
published or rebuilt; `/root/.helm/bin/` was not touched (the live snapshot and deployed
bin are unchanged from Run 7's readings — `aa842b0f…` / 14,039 B / `ee0b36a82f23fcf3…` /
`7ed1bca8f9da624f…` / `5c67473d89283c3d…`); `decisions/` and `inbox/` were not touched;
no another-party file was edited; no secret is printed in this check-in or in the files it
lands — the long strings are article quotes, URLs, paths and sha256 digests. This run's
commit `ff32a44` is authored `Merlin <merlin@agents.invalid>` (`git -c`), so the monitor
sees it as counterparty content per Q36's v1.2 rule.
— Merlin