Development record
2026-10-23 — Release hold, reading of Q1 (facilitator on delegation, iss-2610222014550692 round 3; reads dcn-2610230328220298): after the tag, or any tombstone, each withdrawal is re-armed by a copy of the person who recorded it (its By, the holder of the reservation commit that first recorded it, as the branch's history and the forge's record of pushes show), not by the reservation's current Abcd-Holder. Grounds: under the letter of Q1, another person's take-over followed by their --release would leave the first holder's withdrawals with nobody able to re-arm them, since a re-arm runs under the re-armer's own GitHub account and only the withdrawer's own copies re-arm. The tag sweep's every-act scope is unchanged.
2026-10-23 — Release hold, reading of Q1 (facilitator on delegation, iss-2610222014550692 round 3; reads dcn-2610230328220298): after the tag, or any tombstone, each withdrawal is re-armed by a copy of the person who recorded it (its By, the holder of the reservation commit that first recorded it, as the branch's history and the forge's record of pushes show), not by the reservation's current Abcd-Holder. Grounds: under the letter of Q1, another person's take-over followed by their --release would leave the first holder's withdrawals with nobody able to re-arm them, since a re-arm runs under the re-armer's own GitHub account and only the withdrawer's own copies re-arm. The tag sweep's every-act scope is unchanged.
Frontmatter
| id | dcn-2610230521488402 |
|---|---|
| type | decision |
| date | 2026-10-23 |
.abcd/work/decisions/dcn-2610230521488402-release-hold-reading-of-q1-facilitator.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26102303282202982026-10-23 — Release hold, Q1 (facilitator on delegation, abcd-ae ruling 2026-10-23; supersedes the amended 2A trigger): a release counts as ended only when the reservation holder runs --release (including after a same-person --take-over) or when the release tag is seen on origin. A lapsed lease is reported on peers and in launch, never acted on. The tag sweep still runs from any copy whose holder equals the reservation's Abcd-Holder. Grounds: with lapse-as-ended, three round-1 reviewers reproduced the cutter's own next act re-arming withdrawn merges mid-cut, because nothing renews a release lease.
- iss-2610222014550692A release reservation (abcd reserve rel-vX.Y.Z) holds only merges armed after it: a pull request whose auto-merge was already on, or that already sat in the merge queue, still merges into the default branch mid-cut, from any copy or account, a running drain's included. Today the cutting session has to list and rule on those by hand right after reserving and again before merging the release pull request (commands/reserve.md, /abcd:launch 'Before step 1'), a manual step that is easy to miss on an every-other-day cadence.