Mission Run Overview
Mission Run: Every Mission-file writer takes the lock, and the runtime never cuts a log it cannot prove is its own
Close the follow-ups to concurrent-mission-writers: the last unlocked Mission-file writers, the runtime run-log truncate, and planning-flow friction around the analyze step and feature wording.
PR 5890 added one Mission write lock and a verified rollback, but its scout found more Mission-file writers that still read and write without the lock, the gate has three documented holes, and the runtime rolls its run log back with the same unverified truncate. Running that Mission also surfaced planning friction: generated commits say 'feature', and implement refuses on an analyze step the tasks prompts and spec-kitty next never offer. This Mission closes all three so parallel agents never lose a write and the planning flow tells the operator every required step.