make sending ctrl c on running implement result in switching in-progress label to ready-for-agent label #613

Activity

1. JacobStephens2 commented on Oct 17, 2026

   

   JacobStephens2

   on Oct 17, 2026

   OwnerAuthor

   More actions

   This was generated by AI during triage.

   Triage Notes

   Ctrl-C already restores readiness when nothing was started on origin. After work is preserved on origin, the current Claim contract keeps in-progress for the Day shift. Simply restoring ready-for-agent is insufficient: Pickup still skips an already-started issue, which #617 addresses.

   Decision needed: Should every graceful interruption hand work back, or only an explicit “stop and requeue” action? Define its interaction with #617, failed Security fixes, manual label changes, and interruption at any Run stage. Keep this policy distinct from hard-kill recovery in #710.
2. JacobStephens2

   added

   enhancementNew feature or requestNew feature or request

   needs-triageMaintainer needs to evaluate this issueMaintainer needs to evaluate this issue

   wontfixThis will not be worked onThis will not be worked on

   and removed

   needs-triageMaintainer needs to evaluate this issueMaintainer needs to evaluate this issue

   on Oct 17, 2026
3. JacobStephens2 commented on Oct 21, 2026

   

   JacobStephens2

   on Oct 21, 2026

   OwnerAuthor

   More actions

   This was generated by AI during triage.

   Closing as already implemented as an explicit action. thirdshift stop <command> --requeue, or "Requeue instead" on the Console's Stop page, ends the Run and puts ready-for-agent back in place of in-progress, even when work is on origin. A plain Stop adds needs-triage instead. A Ctrl-C with no Stop keeps the usual Claim rules: the Claim is released only when nothing reached origin. The Claim of a Run killed outright is #710.
4. JacobStephens2

   closed this as completedon Oct 21, 2026