Module report_render 

Markdown renderers for the mission artifacts — plan.md, research.md, revised-plan.md, and report.md — extracted from orchestrator.rs in the monolith split (pure code motion, no behavior change). Everything here is pure and deterministic given its inputs (no wall-clock reads): the orchestrator computes estimates and timestamps and passes them in.

Functions

render_mission_report

Render the mission completion report (roadmap M1): elapsed time and cost vs the pre-mission estimate, what shipped per feature, the validation history including waived findings with their justifications, and the contract outcomes. Committed beside plan.md at mission completion and linked from missions/index.md.

render_plan_markdown

Render the approved plan as human-readable markdown — committed to the mission branch beside plan.json for later review and reference. Pure and deterministic given its inputs (no wall-clock reads; the estimate is computed by the caller and passed in).

render_revised_plan_markdown

Render the revised plan as human-readable markdown for review (roadmap M2), committed to the mission branch as revised-plan.md. Shows the full revised plan plus a “Re-plan changes” section describing the reducer’s merge rules. Older single-milestone re-plan callers can still pass explicit dropped/added feature lists; the event-driven M2 path records the exact structural change in the plan.revised event and folded state.