Development record
abcd land's stacked-branch check runs only before it makes a fresh arming: #1398's stackedOn sits in the arming branch of internal/core/landing/land.go, so it guards neither the 30-minute toggle that re-arms an arming land already made nor the build loop's own land stage (toggleArming in internal/core/implement/loop/queue.go), as the session that wrote it reported. iss-2611031719581061 holds the fresh-arming case.
issueopenminoriss-2611042320148804
abcd land's stacked-branch check runs only before it makes a fresh arming: #1398's stackedOn sits in the arming branch of internal/core/landing/land.go, so it guards neither the 30-minute toggle that re-arms an arming land already made nor the build loop's own land stage (toggleArming in internal/core/implement/loop/queue.go), as the session that wrote it reported. iss-2611031719581061 holds the fresh-arming case.
Frontmatter
| id | iss-2611042320148804 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2611042320148804-land-s-stacked-check-guards-only-a-fresh.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2611031719581061abcd land arms a pull request whose branch carries another queued pull request's commits, and the merge queue then removes it as invalid_merge_commit: on 2026-11-03 #1376 (records-coord-1103c) carried #1375's two commits and was armed while #1375 was queued; it entered the queue at 14:46 and was removed 16 seconds later, missing the 15:00 freeze, and had to be re-armed by hand after #1375 merged.