Interrupting a Spec run #145

Parent

#139

What to build

Interrupting a Spec run is safe. Ctrl-C, SIGTERM or a closed terminal reaches every Ticket's Run (they share the Spec run's process group, and a signal the Spec run alone receives is passed on to them). Each Ticket's Run ends through its own Failed run path, pushing its work. The Spec run starts no further Ticket Runs and no Spec review, waits for every child to finish, and then ends as an interrupted Failed spec run, printing its summary and exiting 1.

A Spec run interrupted during the Spec review or the Spec PR's Repair loop fails as a Run interrupted at that point does.

Acceptance criteria

• SIGTERM to the Spec run while two Tickets run ends both Ticket Runs through their Failed run path, with their work pushed to origin
• No Ticket Run and no Spec review starts after the interrupt
• The Spec run exits only after every Ticket Run has ended, with exit 1 and the summary marking it interrupted
• SIGHUP (a closed terminal) behaves the same
• An interrupt during the Spec review ends the Spec run with exit 1 and the Spec PR not marked ready

Blocked by

• Tracer bullet: a linear Spec run to a ready Spec PR #141