Development record
abcd reserve, run from a sibling worktree of the checkout that holds a person's live reservation, refuses with 'you are already building <id> on another computer', and the release merge hold reads 'being cut by your copy on another computer' the same way. The copy key lives in each worktree's own local tier, so every worktree is its own copy and the words are false for the commonest case, a second worktree on the same machine: on 2026-10-25 a renewal from the lane's worktree was refused that way, and only trying the main checkout found the copy that held it. The footprint refusal does not say that a renewal by hand, the same command again, names the footprint too.
abcd reserve, run from a sibling worktree of the checkout that holds a person's live reservation, refuses with 'you are already building <id> on another computer', and the release merge hold reads 'being cut by your copy on another computer' the same way. The copy key lives in each worktree's own local tier, so every worktree is its own copy and the words are false for the commonest case, a second worktree on the same machine: on 2026-10-25 a renewal from the lane's worktree was refused that way, and only trying the main checkout found the copy that held it. The footprint refusal does not say that a renewal by hand, the same command again, names the footprint too.
Grounds
- pursued: every refusal and hold the person's sibling worktree causes names that worktree; one still reading another computer for a sibling shows it wrong
Frontmatter
| id | iss-2610250013552001 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610250013552001-abcd-reserve-run-from-a-sibling-worktree.md
open on GitHub ↗ · commit history ↗