Two matched worktree methods exist (refresh onto the base vs resume onto the pushed branch): same ordering, different commit resolved. The resume half is wired to the wrong caller, so the retry path cannot choose to continue pushed work, and a second resume implementation (the hybrid trees one) is a no-op.
Acceptance criteria
The retry path can select the mode; the no-op implementation is either wired or deleted; red-first test per mode
Close reason
Closed
Imported from beads archie-core-866m · GitHub #1463 · type bug · priority P2 · created 2026-10-02 · closed 2026-10-02
Two matched worktree methods exist (refresh onto the base vs resume onto the pushed branch): same ordering, different commit resolved. The resume half is wired to the wrong caller, so the retry path cannot choose to continue pushed work, and a second resume implementation (the hybrid trees one) is a no-op.
### Acceptance criteria
The retry path can select the mode; the no-op implementation is either wired or deleted; red-first test per mode
### Close reason
Closed
---
_Imported from beads `archie-core-866m` · GitHub #1463 · type bug · priority P2 · created 2026-10-02 · closed 2026-10-02_
sam
added the mediumbug labels 2026-10-27 13:39:10 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two matched worktree methods exist (refresh onto the base vs resume onto the pushed branch): same ordering, different commit resolved. The resume half is wired to the wrong caller, so the retry path cannot choose to continue pushed work, and a second resume implementation (the hybrid trees one) is a no-op.
Acceptance criteria
The retry path can select the mode; the no-op implementation is either wired or deleted; red-first test per mode
Close reason
Closed
Imported from beads
archie-core-866m· GitHub #1463 · type bug · priority P2 · created 2026-10-02 · closed 2026-10-02