Lanes lose whole preflight slots to repo-wide audit tests that fail late. A preflight queues behind every other preflight on the machine (an hour or more on 2026-10-22), then spends its first long stretch on the unit stage before a test that reads the whole tree fails on a sentence: TestSurfaceChapterProseStatesNoShape failed two lanes' preflights on 2026-10-22, each for a command name in the build brief's prose, and the lane then had to queue again from the back. The same lesson came up on 2026-10-18, when lanes were tested package by package and missed the repository-wide audit tests until preflight. Nothing lets a lane run the fast, repository-wide gates and audit tests on their own, in seconds or a few minutes, before it takes a preflight slot.

Frontmatter

.abcd/work/issues/resolved/iss-2610230016523625-lanes-lose-preflight-slots-to-repo-wide.md
open on GitHub ↗ · commit history ↗

mentions1

• iss-2610230826159867A resolved issue's resolved_by.commit goes stale when the commit it names is rewritten before it reaches the default branch, and nothing follows it. On 2026-10-22/23 lane C re-stamped records by hand three times: twice after rebasing a stacked branch onto a moved parent, and once after re-wording an unpushed commit to drop a scoped prefix. Each time RS003 found the stamp unreachable and the ledger gate failed until the sha was edited by hand. Two designs are open and not chosen here. A lookup by patch-id follows a reworded or rebased unpushed commit to its new sha, but does not survive a squash merge, which already rewrites the cited commit out of existence and which RS003 reports. Stamping at land time instead (resolve names the change, the land step writes the merged sha) survives a squash but needs the land step to own the stamp.