Development record
The sessions-announce intent promises every session's merge waits out a release cut; the reserve brief says merges armed before the hold still land
The sessions-announce intent promises every session's merge waits out a release cut; the reserve brief says merges armed before the hold still land
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-2609151838312703-sessions-announce-what-they-are-doing.md:22— "A session cutting a release holds merges with a reservation everyone sees, and every session's merge step waits until the cut is done." - End B:
.abcd/development/brief/04-surfaces/37-reserve.md:357— "A merge armed, or queued, before the release was reserved (a pull request with auto-merge on, or an entry already in the merge queue) is not stopped by it and lands when its checks pass."
The intent's press release says a release reservation makes every session's merge step wait until the cut is done. The reserve chapter says the hold only stops a merge from being armed. A pull request with auto-merge already armed, or already in the merge queue, when the release is reserved is not stopped and lands when its checks pass. Someone building from the intent would expect no merge to land during a cut, but the brief says some can.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 724.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262033053387. Same overreaching press-release promise checked against the reserve chapter instead of the launch page.
Frontmatter
| id | iss-2610262037274982 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262037274982-the-sessions-announce-intent-promises.md
open on GitHub ↗ · commit history ↗
References1
- itd-2609151838312703Sessions under any account, on any machine or in the cloud announce what they are doing through short fixed-form announcements on the shared remote, a person reads everyone's status with one command, and what is really a hold stays a reservationrelated
mentions2
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- iss-2610262033053387The announcements intent promises that nobody's session merges into a release being cut; the launch page says the release hold does not stop a merge armed or queued before the reservation.