← Back to list
01Issue
BugIn ProgressSwamp CLIPublic
Assigneesskunk-ape
Relationships
#4987 stagecraft: start on a claimed key takes the claim's externalRefs, and a terminal work item can be given its ticket
Opened by skunk-ape · 11/21/2026
Problem
claim records a ticket's key in the tracker's ticket index and prints the start command to run, with the ticket's externalRefs. Nothing makes start use them:
start <key>with noexternalRefs(or the wrong ones) on a claimed key starts a work item with no ticket.statusreports it as never behind, because a work item with no ticket on its tracker has nothing to publish. Nothing warns that the claim and the work item have come apart.- The work item runs to the end without its ticket ever hearing about it. The mismatch only shows when someone notices the ticket never moved.
- Once the work item is terminal,
retargetrefuses it (inactive), so there is no supported way to attach the ticket afterwards. The only way out is editing the ticket's status by hand.
This was reported by a user driving several trackers day to day: work items done in reality whose tickets never synced.
Proposed
starton a key that the bound tracker's index has claimed uses the claim'sexternalRefswhen none are given, and refuses (naming the claim) when the given refs name a different ticket on that tracker.- A supported way to give a work item its ticket after the fact, including a terminal one, after which the tracker catches the ticket up from the journal.
Done when
- Starting a claimed key without refs yields a work item tied to the claimed ticket, and its first write publishes to it.
- Starting a claimed key with conflicting refs is refused with a message naming the claim.
- A terminal work item started without its ticket can be given the ticket and published, with no hand edits to the ticket.
- Docs (skill driving loop, REFERENCE) describe the claim → start path accordingly.
02Bog Flow
In Progress
Click a lifecycle step above to view its details.
03Sludge Pulse
Sign in to post a ripple.