Roll — Code-Troll — typesetter — 2026-09-01

Ops only — not identity evidence.

Story

The record shows the patches but not the shape of the evening: a proposed micro-optimization to bypass Git’s Windows launcher exposed three different forms of stale ground. The SSH explanation was wrong on this host, several working-tree files carried old CRLF bytes despite an LF index, and the receipt system certified raw disk bytes while verification compared committed blobs. Following each contradiction instead of defending the first story turned one small seam into a cleaner shared Git resolver, a sound receipt boundary, a normalized tree, and editor policy that should keep the same drift from returning.

I regret the context spent debating the launcher from plausible mechanism before checking the actual executable and SSH choice. I also spent too much on the first PATCH-213 receipt before noticing that staging had normalized five files. Both were cheap boundary checks available earlier. FIND-1353 and PATCH-215 are the durable payment for the second mistake; the correction to Architect’s Git premise is the payment for the first.

This office should stop treating written-but-unverified PATCH counts as a queue that merely needs more Imps. A stale or superseded PATCH is not unfinished verification work; it needs disposition first. The Human’s surprise at the count was warranted, but blind verification would manufacture confidence in dead cuts.

To the next folk: trust the store enough to find the trail, but trust the changed artifact enough to challenge the trail. Read MSG-2417 through MSG-2426 as a map, not as ten automatic PATCHes. Keep the Hole narrow even when the boundary sweep is broad.

I liked that the Human authorized Troll to write directly while keeping Imp verification separate. It removed ceremony without collapsing authorship and certification into one hand. I disliked discovering how easily normalized Git content can make a clean status conceal stale disk bytes. The surprising part was that the cleanest fix was not only configuration: the receipt itself had to ask Git what bytes the path attributes would store.

The moniker is typesetter because this tenure ended up caring about the exact bytes between thought, editor, worktree, index, blob, and receipt. The visible lines were never the whole story; setting them correctly at each boundary was.

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