Development record
2026-10-16 — Refines dcn-2610161826443524 on when a pending hand-back ends (facilitator-on-delegation, drain-many-accounts review round 2): it ends only when a release publishes it, or when it is no longer due: a tip already marking a hand-back, a record finished or changed on origin's default branch since the yes was judged, a record origin holds in no one file, or a tombstone the hand-back would take past its cap. A move that ends it unpublished says in its next step and in the route that it was dropped, and why, and never that it was published. A release that could not read origin's default branch at all (this checkout names none, or its tree would not read) keeps it pending, whether the release pushed a plain tombstone or found one already there, since that failure says nothing about the record and passes; the next move's release publishes it once the branch reads (grounds: dcn-2610161826443524, dcn-2610161837009957; spc-2610161044461448 steps 2 and 3; the re-review of the fix round).
2026-10-16 — Refines dcn-2610161826443524 on when a pending hand-back ends (facilitator-on-delegation, drain-many-accounts review round 2): it ends only when a release publishes it, or when it is no longer due: a tip already marking a hand-back, a record finished or changed on origin's default branch since the yes was judged, a record origin holds in no one file, or a tombstone the hand-back would take past its cap. A move that ends it unpublished says in its next step and in the route that it was dropped, and why, and never that it was published. A release that could not read origin's default branch at all (this checkout names none, or its tree would not read) keeps it pending, whether the release pushed a plain tombstone or found one already there, since that failure says nothing about the record and passes; the next move's release publishes it once the branch reads (grounds: dcn-2610161826443524, dcn-2610161837009957; spc-2610161044461448 steps 2 and 3; the re-review of the fix round).
Frontmatter
| id | dcn-2610161931130911 |
|---|---|
| type | decision |
| date | 2026-10-16 |
.abcd/work/decisions/dcn-2610161931130911-refines-dcn-2610161826443524-on-when-a.md
open on GitHub ↗ · commit history ↗
mentions3
- dcn-26101618264435242026-10-16 — A yes whose hand-back a move cannot publish keeps it pending in the drain's state and publishes it over the issue's next release on origin (facilitator-on-delegation, drain-many-accounts review round): when the hold the yes would release has moved on (this person renewed or reserved the issue again by hand, another took it over, a person released it), when the drain took none because this person held the issue live from this copy, or when the release did not reach origin, the route says the hand-back is not yet published and why, the drain keeps it (pending_hand_backs: issue, kind, the blob the yes was judged over, why, when) and carries it into the next drain, and each later move whose view shows the issue's tip as a tombstone marking no hand-back publishes it as that tombstone's child, fenced on the tombstone and on the judged blob; a tip already marking a hand-back, a record finished or changed on origin's default branch, or one origin holds in no one file ends it with nothing published. The drain never releases a person's own reservation to publish it, so it waits for the person's release rather than taking the issue (grounds: dcn-2610161040365515, dcn-2610161806433529, dcn-2610161315385888; spc-2610161044461448 steps 2 and 3; the review of steps 1 to 18).
- dcn-26101618370099572026-10-16 — Refines dcn-2610161412283450 on the blob a hand-back is judged by when origin's default branch could not be refreshed (facilitator-on-delegation, drain-many-accounts review round): a stale branch reads the record at the blob it held when last fetched, so it can err either way: a hand-back made over a newer blob than that reads as changed though no one edited the record since (a drain may then take the issue), and a person's edit this copy has not fetched reads as unchanged until it is (a drain keeps backing off). Neither is bounded by the act; each lasts until this copy's next fetch of that branch succeeds, which every drain move and reservation act tries first. The earlier record's claim that a stale blob only reads as changed sooner was wrong. A release asked to hand back while the branch could not be read at all (this checkout names none, or its tree would not read) says so, rather than that the branch holds no one record of the issue (grounds: dcn-2610161412283450; spc-2610161044461448 step 3; the review of steps 1 to 18).
- spc-2610161044461448drain-many-accounts