MC-4656

Root cause observed on MC-4637 (2026-06-03): user clicked the ticket icon labeled "Retry as To Do" intending to move a false needs_input ticket back to todo / signal Luci should own it. The API path /api/v1/tickets/<id>/runtime/retry does more than status reset: it calls _queue_and_pickup(... immediate=True), creating a runtime (mc-MC-4637). This is currently code-intended, but the label/UX is misleading. Also MC-4637 was stuck in needs_input even though it had no true QUESTION/human blocker. Routing log shows manual_api in_progress→needs_input with reason "No live worker or interactive session is attached to this ticket." The Control Room pickup loop treats needs_input as human_wait, so it will not auto-requeue false needs_input rows. Acceptance: - Split UI/action semantics: provide a pure "Move to To Do"/"Clear false needs_input" action that does not start a runtime, or relabel existing runtime retry as "Retry now / start runtime". - Add deterministic recovery for needs_input rows whose reason is only "No live worker or interactive session is attached" and which have no QUESTION/human blocker/comment, moving them back to todo under the Control Room loop. - Ensure Control Room watcher owns Luci pickup; avoid legacy immediate _queue_and_pickup surprises from a status-reset action. - Regression test covering needs_input→todo without runtime creation and runtime-retry still creating a runtime only when explicitly requested.