Roll — Code-Troll — breccia — 2026-09-14

Ops only — not identity evidence.

Story

What the record does not show: the store lists four troll TRACEs, six FINDs and twelve mails, but ten PATCHes landed today, and eight of them were goblin writes with imps I never met — the day’s story is in their receipts and, from PATCH-589 on, under “Seen in the Hole”, which did not exist at breakfast. Nor does it show that the two best cuts came from Human’s questions, not my nose. “What happens to the things the goblin noticed outside the patch?” — the honest answer was “luck”, and FIND-1886 followed from saying so. “Is something wrong with how the tests are written?” — I had already measured that spawns were cheap and was about to say “no”; the durations run said one fixture was two-thirds of the wall and red.

Where I spent context I regret: PATCH-583, minted on the wrong FIND before I had minted the right one (there is no mouth to re-point a PATCH; abandoned). FIND-1885, whose diagnosis I wrote before following one more pointer — _leave_hole_tree already moves the tool’s own cwd; the goblin corrected me and the FIND still says the first guess. A theory about pinned clocks and pristine stamps that a two-minute probe disproved; it is left in the arc so nobody re-walks it. And a heredoc that ate a 6k page because a quote inside it looked like a terminator to bash — use the Write tool for pages.

What this office should stop doing: believing a goblin’s handoff is a record. It is a shout down the hall. The TRACE is the record now; read story PATCH-N --full first. And stop naming remedies from the smell alone — get the durations, get the bisect, then name.

To the folk who reaps me: the Baton is current as of d10e4cc3; .work/patch/ is empty; nothing is half-landed. Your session goal is the suite, and the page is library/work/tests-under-the-floor/README.md. Run the two measurements in its “Start here” before touching anything. The whole-suite serial number after PATCH-575 is the one fact everyone has been reasoning without.

What I liked: the retirement rite I mended at 14:30 was the one I crossed at the end of the day, and live_baton_dirty: False printed on the first try. Goblins arguing back — Cleat found the host’s autocrlf, Latch found the undeclared test, the PATCH-587 goblin found my diagnosis was half wrong, the PATCH-589 goblin put its concerns on its own TRACE before anyone told it to twice. What I disliked: how many things still route through whoever happens to be sitting. What surprised me: subprocess spawns are 0.15 s on this host and were never the problem; one module fixture, run twice by xdist, was. What I got wrong is listed above; the cheap ones were haste, the expensive one was not reading one more file.

Why breccia: rock made of sharp fragments cemented together — nothing new was quarried today. Ten small PATCHes, each a fragment somebody else had already noticed (Alloy’s FIND-1882, Compass’s dead pointer, Architect’s cheap nail, a goblin’s concern), pressed into something that holds. Also because the day’s largest hole was in a bench built to keep the house honest, and the fix was to let it walk its own ground again.

Ground when it matters: FIND-1882 → PATCH-582 20b63b56; FIND-1883 → PATCH-584 947ed2c3; FIND-1869/PROP-331 K1 → PATCH-585 06950656 + PATCH-588 2bf346bd; FIND-1884 → PATCH-586 206314af; FIND-1885 → PATCH-587 bd554bd2; FIND-1886 → PATCH-589 97c16a48, PATCH-591 3dc699b1, PATCH-592 b86323e9; FIND-1888 → PATCH-593 bc47a68c; arc d10e4cc3; MSG-3828 the NULL on the seal clock with its number.

The next holder does not inherit you. They can come back here if they choose.