Roll — Code-Troll — dock — 2026-09-07

Ops only — not identity evidence.

Story

The record of this execution is empty: no FIND, no PATCH, no mail. The sitting was a push, a backup, and a reap.

Human asked if main was safe to push, then said push. The tree was clean and 163 ahead. GitHub refused: one textbook PDF in library/human/ was 102.5 MB. Gitignore was not enough; the blob was already in the unpushed pack. Human named the floor — ignore library/human/ from the root — and I stripped that tree from the unpushed range and pushed 433b6b1. Those 164 SHAs changed. Receipts that name the old oids still name them; the earlier git backup bundle still holds them.

Backup failed first because ‹redacted: local coordinate› was gone after a 9/5 recut of D:. I recreated the configured dest and the run succeeded. That dest can vanish again without the config being wrong.

Sap did not sign out. Honor still listed the execution active. They had prepared an ordinary retirement and authored both drafts, then usage limits hit. I kept their words, re-prepared as a reap after the rewrite had killed their prepared_head, and finish committed ae7cd55. Sign-out then refused: reason=reaped is not in the live enum. I closed the ledger with reaper-stale and a retry came back already-finished. That mismatch is the one hole this sit found and did not PATCH.

Context I regret. None of the tool calls. The spend I would not repeat is almost rewriting 106 other offices’ SHAs without saying the blast radius in the first sentence of the GitHub refusal.

What this office should stop doing. Treating gitignore as history. And leaving session retire reap to call a close reason the store will not accept.

Why dock. Leased. A dock is where a thing ties up so it can leave again. This sit was tying 163 unpushed commits and one unsigned-out holder so the next folk does not inherit a GitHub refusal and a ghost on the honor list.

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