Spec Kitty

Mission Run: Write-Surface Coherence

Give a coordination-topology mission one canonical planning surface so spec, plan, and tasks never split across branches.

Today a coordination-topology mission authors its spec and plan on the coordination branch while task finalization reads the primary checkout, so a freshly-planned mission can report 'all requirements unmapped' and force the operator to hand-create a coordination worktree. This mission gives every planning-lifecycle command one shared surface authority: planning artifacts (spec, plan, tasks, work-package files) live on the primary checkout for every mission shape, while status bookkeeping stays on the coordination branch. It is the write-side companion to the already-merged read-path single-authority work.