An issue lane whose widening backed off (abcd implement widen, exit 3) has its implement stage handed out again at the very next step, with no wait for the hold that refused it to end: a host or runner stepping the run dispatches a fresh implementer that meets the same hold, as often as it steps, spending an agent each time on a lane that should wait for another copy's hold to end. A runner's end without a receipt is refused outside the step that counts refusals, so nothing bounds the repetition either.

Frontmatter

.abcd/work/issues/open/iss-2610311604123786-an-issue-lane-whose-widening-backed-off.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.