Development record
A peer's announced record freeze cannot hold pull requests that were armed for auto-merge before it began. On 2026-10-10 a session opened a freeze so it could rename every record with a long slug (#904), and the drain session parked its new lanes. But a drain lane PR (#901), armed by the implement loop's landing an hour earlier, merged through the queue during the freeze. Its record move under the old long name broke #904's queued tree, which dropped #904 from the queue and cost about an hour of re-merging and re-queueing. Nothing listed the PRs each session had armed, and nothing let the freeze disarm them.
A peer's announced record freeze cannot hold pull requests that were armed for auto-merge before it began. On 2026-10-10 a session opened a freeze so it could rename every record with a long slug (#904), and the drain session parked its new lanes. But a drain lane PR (#901), armed by the implement loop's landing an hour earlier, merged through the queue during the freeze. Its record move under the old long name broke #904's queued tree, which dropped #904 from the queue and cost about an hour of re-merging and re-queueing. Nothing listed the PRs each session had armed, and nothing let the freeze disarm them.
Frontmatter
| id | iss-2610102142432879 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610102142432879-a-peer-s-announced-record-freeze-cannot.md
open on GitHub ↗ · commit history ↗