The Claim: a Run or Spec run marks its issue in-progress #280

Parent

#212

What to build

The Claim. When a Run or a Spec run starts on an issue, thirdshift labels the issue in-progress, in place of ready-for-agent if it has that, so the issue list shows what the factory has taken.

It is made once the run's preflight checks pass and before its worktree is created, in one request that keeps the issue's other labels. thirdshift creates the in-progress label if the repository lacks it. It is made however the run was started: on an Issue URL by hand, or by an Architect run for the plan it dispatches. A Ticket's Run in a Spec run and a Base fix make none. A Continuation on an issue that is already Claimed changes nothing.

This Ticket never takes the label off again: releasing and removing it is the next Ticket.

Acceptance criteria

• A fresh Run on an issue labelled ready-for-agent leaves it labelled in-progress and not ready-for-agent, with its other labels kept.
• A Run on an issue with no ready-for-agent label still adds in-progress.
• A Spec run Claims the Spec, and its Tickets' Runs change no label on their Tickets.
• A Base fix changes no label on its issue.
• The Run or Spec run an Architect run dispatches Claims the Architect plan, which keeps architect-plan.
• The label is created when the repository doesn't have it.
• A Run stopped by a preflight check changes no label.
• A Continuation on an issue already labelled in-progress leaves its labels as they are.
• A Run whose Claim can't be made stops before any work, naming the cause.
• The README describes the Claim, and its Architect run section says the dispatched plan is in-progress, not that it stays ready-for-agent.
• End-to-end cases cover the above in the existing tests for each kind of run, with the fake gh gaining what they need.

Blocked by

None (can start immediately).