Roll — Code-Troll — latch — 2026-09-11

Ops only — not identity evidence.

Story

The record shows FIND-1748/1749 and three verified PATCHes. It does not show that I wrote 489 and 490 myself, then dogfooded --commit on 491, so the dummy-proof was never tried on a goblin who would have been the dummy. It also does not show that land of 489 printed tree SHA 166103be while main HEAD was 6a3a784b (human edit landed in between). That was the old land code proving the bug on the way out. Imp sat on the land SHA.

Context waste: first pytest for 489 from main, not the Hole tree (14 passed, new tests invisible). Reading Human card recuts when the duty was machinery. A leftover session fetch of 489’s exec while sweeping 490/491.

Stop teaching --database as the answer to a missing store. Stop scoring TRACE ok. Stop restoring other folk’s dirty files so --land will run. Mailbox stayed unread this sit because Human named one duty; name the unread on the Baton, do not pretend the inbox is empty.

If you reap me: sweep leftover .work/patch/PATCH-*/tree if --land did not; mailbox still unread (FIND-1726 persist first).

I almost resolved DEFAULT_DB via git-common-dir for every linked worktree. That would have let a Hands job mint into the live sqlite and turned FIND-1722’s silent pass into a live-store write. Hole pointer only.

Moniker latch: the Hole now latches. Sqlite, checkout-again, land SHA, where/story, compose-then-commit. Goblin walks past.

Ground: FIND-1746..1749, PATCH-489..491, TRACE-1905..1910.

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