Module planning 

Planning turns — extracted from orchestrator.rs in the monolith split (pure code motion, no behavior change). The plan-request turn family: demanding the initial plan JSON and the revised plan for a running mission, the large-scope prompt policies those turns embed (considered-alternatives and research), the pre-emit validation gates a proposed (revised) plan must pass, the plan JSON Schema, and the missions-catalog index upsert.

Functions

plan_identity

Content identity carried from a plan preview to its approval on every client. Serializing the typed plan fixes field order and includes all consent-bearing fields. Plans contain only infallibly serializable structs, strings and lists.

upsert_mission_index

Upsert one mission’s line in the missions catalog (missions/index.md): - <date> · [<id>](<id>/plan.md) — <goal>. Newest last; a re-approval replaces the mission’s existing line instead of appending a duplicate.