Mission Run Overview
Mission Run: Runtime-State Birth-Cutover (All Landing Paths)
Every mission is fully cut over to the event-sourced runtime-state model the moment it lands on main, regardless of how it was merged, so releases are never re-blocked by corpus drift.
Missions record runtime state as an event log that must be 'cut over' (status_phase stamped plus deterministic seed events, verified) to count as migrated. Today that stamp fires on only one of the two ways a mission's corpus can reach main; missions merged the other way (GitHub-side squash/rebase) arrive un-migrated and silently red a release-gating test, forcing a manual re-green each time. This mission makes the cutover happen across every landing path and adds a fail-closed guard that blocks any un-migrated mission from reaching main, so the release can no longer be held hostage by this recurring drift.