Development record
The live-reservation cap refusal drops the reason the sibling worktrees could not be listed (Snapshot.SiblingsUnread), so a sibling's hold is grouped under elsewhere with no word why, and its copy labels are keyed by record id with no holder or live-state filter, so another holder's tip on the same record could relabel the reader's own
issueresolvedminoriss-2610272352179242
The live-reservation cap refusal drops the reason the sibling worktrees could not be listed (Snapshot.SiblingsUnread), so a sibling's hold is grouped under elsewhere with no word why, and its copy labels are keyed by record id with no holder or live-state filter, so another holder's tip on the same record could relabel the reader's own
Frontmatter
| id | iss-2610272352179242 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610272352179242-the-live-reservation-cap-refusal-drops.md
open on GitHub ↗ · commit history ↗
mentions1
- dcn-26102723522496012026-10-27 — Peers-cap review notes deferred past its landing (lane D, facilitator on delegation, 2026-10-27): the rebased review pair of fix/peers-cap-warning returned LAND-WITH-NITS from both reviewers with no blocker. Its one display gap, the ceiling's note missing from the text form, is fixed on the branch. Three notes are captured and deferred to a follow-up change: iss-2610272352153282 (one sibling named two ways), iss-2610272352168723 (clashing sibling names merged) and iss-2610272352179242 (the cap refusal drops the listing note and labels copies without a holder filter). Grounds: none changes a count, a refusal or a reservation, only how a hold's copy is named; peers-cap resolves the major that blocks the release (iss-2610231004140527); and the first needs one worktree listing shared with the default branch's sibling naming, a refactor across both that wants its own review rather than a fifth round on this one.