Mission Run Overview
Mission Run: Next Resolves State From Committed Authority
spec-kitty next reads committed mission status and operator provenance — never a stale worktree or lane alone — so merged missions aren't restarted and operator-canceled work doesn't stall the loop.
When a mission has already merged, or an operator has deliberately canceled a work package, the mission loop should recognize that from the authoritative committed record. Today it can instead read a stale coordination checkout or a lane value in isolation, causing it to restart finished work or refuse to move past an honest ending. This mission routes the loop's state decisions through committed status and the existing operator-provenance authority, and fails closed (blocked/error) when the workspace is stale or missing artifacts rather than pretending the work never started.