Development record
2026-10-23 — The finding in iss-2610230927379322 is deferred out of the release-hold change (iss-2610222014550692), ruled by the coordinating facilitator on delegation while the product thinker is away: the merge hold that abcd land respects still reads any tombstone on a release reservation as the release's end, whoever pushed it, so land and the launch check can disagree about one release. Reason: the land hold already ends when its lease lapses, so it is a time-boxed courtesy; the withdrawal the release-hold change adds is what keeps merges out; and a change to every land check deserves its own review. The same session fixes it as its first work once the release-hold pull request lands, not at a later date.
2026-10-23 — The finding in iss-2610230927379322 is deferred out of the release-hold change (iss-2610222014550692), ruled by the coordinating facilitator on delegation while the product thinker is away: the merge hold that abcd land respects still reads any tombstone on a release reservation as the release's end, whoever pushed it, so land and the launch check can disagree about one release. Reason: the land hold already ends when its lease lapses, so it is a time-boxed courtesy; the withdrawal the release-hold change adds is what keeps merges out; and a change to every land check deserves its own review. The same session fixes it as its first work once the release-hold pull request lands, not at a later date.
Frontmatter
| id | dcn-2610230928271939 |
|---|---|
| type | decision |
| date | 2026-10-23 |
.abcd/work/decisions/dcn-2610230928271939-the-finding-in-iss-2610230927379322-is.md
open on GitHub ↗ · commit history ↗
mentions2
- 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.
- iss-2610230927379322The merge hold that abcd land respects (claim.Hold, read by releaseHolds) still reads a release as ended as soon as any tombstone sits on its reservation branch, whoever pushed it. The release hold now ends a release only on a tombstone its holder pushed or on its tag, for the second-release refusal, the launch reading and peers, so the two readings of one release can disagree: land lets merges through while the launch check still names the release as being cut. The land hold already ends when its lease lapses, so it is a time-boxed courtesy and the withdrawal is the hold that keeps merges out; the disagreement is in what each surface reports.