A build or drain lane whose footprint overlaps a peer's live reservation backs off with exit 3, and nothing tells it when the reservation is released: on 2026-10-24 a planned build waited on a drain lane's reservation of internal/core/implement/loop, and the two sessions coordinated by cross-session messages, the drain promising to say when it released. A session with no peer messaging, or a hosted one, can only poll abcd peers.

Frontmatter

.abcd/work/issues/open/iss-2610241424428420-a-build-or-drain-lane-whose-footprint.md
open on GitHub ↗ · commit history ↗

mentions1

• iss-2611011010338815A back-off leaves no trace: when abcd reserve or a build backs off another copy's live hold (exit 3), nothing is written that the holder or another copy can read (a build lane's widening back-off is noted only in that lane's own local run record), so neither the holder nor a person can later tell who was held back, from which paths, or whether they tried again once the hold ended. On 2026-10-31 a hand reservation of iss-2610311224444576 held eleven record files it never changed for almost four hours (23:09:38Z to 03:06:16Z); answering who that held back took a hand search of every reservation chain on origin, every local run record and origin's history, which found none, and could not rule out a refused attempt on another machine or account, since a refusal pushes nothing. Two open records touch neighbouring parts of the same remedy: iss-2610241424428420 (nothing tells a backed-off build or drain when the hold is released) and iss-2610311604123786 (a widening's back-off is re-handed with no wait); a fix here should build on them, not repeat them.