close-milestonelisted

# Close a milestone <HARD-GATE>The target Milestone must have at least one ROADMAP end-to-end acceptance scenario covering its full owned outcome. Every task owned by `target_milestone_id` must be `closed` on one `shared_baseline_anchor`, whose value is the shortest unambiguous commit reference; its integration queue and active lanes must be empty; every in-scope AC and ROADMAP scenario must map to evidence; and every executed task must link `execution/<card_id>/Card.md` plus a closed `Log.md` current snapshot and final evidence. Downstream work does not block unless it proves an in-scope criterion remains undecided or unproved. Otherwise return to `run-task` or revise the owning authority.</HARD-GATE> ## Reconcile the closing commit The primary orchestrator records the Goal/Requirement/Design/applicable Contract/Task commits and checks: - all target tasks and their execution pointers; - Card completion contracts against Log current evidence; - ROADMAP acceptance scenario → Goal slice → AC → task → test → evidence coverage; - every ROADMAP deliverable against its accepted result and required canonical pointer; - every retained Contract ID against its provider implementation, every in-scope consumer, conformance/integration evidence, and observable failure behavior; - no target lane, lock, accepted candidate, or queue entry remains outside the shared baseline; - known debt and material risk are classified without silently waiving an AC. The Design-stage Contract was an