Stop for Spec runs, Pickup runs and Passes #774

Parent

#711

What to build

A Stop works on every kind of Command, not just a Run started on its Issue URL.

• Spec runs. Stopping a Spec run ends its Tickets' Runs with it, through the existing forwarding of an interrupt. The Spec's issue takes the Stop's labelling. Tickets make no Claims, so their labels don't change.
• Pickup runs. Stopping a Pickup run applies the Stop to the issue it took, Spec or not. This is the case from 2026-10-08 in make a way to easily see in progress thirdshift runs on machine and cut one off #574.
• Passes with no issue. Stopping an Architect run in its Architecture review, or a Security run, ends it without touching any labels.
• Ticket Runs. stop on a Ticket's issue is refused, naming the Spec run to stop instead. Stopping one Ticket's Run is a separate issue.

Acceptance criteria

• Stopping a Spec run with two Ticket Runs running ends both. The Spec's issue gets needs-triage, and the Activity log has one stopped line.
• Stopping a Pickup run that is running a Run labels that Run's issue the Stop's way. --requeue puts it back in line.
• Stopping an Architect run during its Architecture review ends it and changes no labels.
• stop on a Ticket's issue is refused, naming its Spec run, and no signal is sent.
• End-to-end tests with the existing fakes, building on the interruption cases in the Spec run tests.