2026-10-17 — A re-admitted issue's newer run is the issue's run for every verb (facilitator-on-delegation, drain-many-accounts, spc-2610161044461448 step 16 fix round; refines dcn-2610170750411628): an issue run whose lane was handed back and that a newer run of the same issue has followed is superseded, so abcd build <iss-N> resumes the newer run, and a step or a run record read with no run named addresses it, the superseded run no longer counting as one in progress; a handed-back run with no newer run is resumed by build as before; and a drain passes over every run of an issue that was not handed back, complete runs included, so it never opens a second run or a second pull request for an issue whose pull request may still be open (grounds: once re-admitted, the newer run holds the issue's work and reservation, and the handed-back one has nothing left to run; a complete run's pull request settles the issue; review findings 4 and 5 of the step 14 to 18 fix round)

Frontmatter

.abcd/work/decisions/dcn-2610170945378977-a-re-admitted-issue-s-newer-run-is-the.md
open on GitHub ↗ · commit history ↗

mentions2

• dcn-26101707504116282026-10-17 — A running drain's new pace and its re-admissions (facilitator-on-delegation, drain-many-accounts, spc-2610161044461448 step 16; refines dcn-2610161040399117): every lane a drain opens starts on the pace stored in the drain's state, with the layer and origin the drain resolved, never on what the configuration resolves at the lane's start; a running drain takes --fix-rounds as well as --pace and --sub-agents, since the fix rounds are the pace's fourth number set alongside it (ruling DR1), each number named replacing the stored one and the rest kept, written to the drain's state and to each in-progress lane's run pace, which that lane's next stage reads; a route keeps the blob of the issue's record on origin's default branch, and the drain re-admits a handed-back issue once that blob differs, an answer taken before the hand-back deciding nothing; an issue run whose lane was handed back is over for the drain alone, so the drain neither passes the issue over for it nor resumes it and opens a new run, while abcd build keeps resuming it as before; without origin nothing records a change, so a handed-back issue and an issue whose run here is over stay passed over (grounds: a setting the person gives is the drain's for its whole life; a changed record is a new question, read from the same blob the tombstone carries; a change confined to the drain leaves build's resume untouched; iss-2610161015417715, iss-2610161015457468)
• spc-2610161044461448drain-many-accounts