close-milestonelisted

# Close a milestone <HARD-GATE>The target ROADMAP Milestone must currently have `state: initiated` and `accepted_result: none`. 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 ROADMAP deliverable and success signal must map through Goal Close outcomes and in-scope ACs to sufficient evidence; and every executed task must link `execution/<card_id>/Card.md` plus a closed `Log.md` current snapshot and final evidence. A required product, integration, regression, recovery, or E2E path still needs evidence when Goal or Requirement makes it part of Close. Downstream work does not block unless it proves an in-scope criterion remains undecided or unproved. Otherwise return to the owning stage before closure.</HARD-GATE> ## Reconcile the closing commit The primary orchestrator records the exact Goal/Requirement/Design/applicable Contract/Task commits and machine state, then checks: - all target tasks and their execution pointers; - Card completion contracts against Log current evidence; - ROADMAP deliverable and success signal → Goal Close outcome → AC → sufficient evidence coverage; Task, test, and E2E are included only when applicable to that evidence; - every ROADMAP deliverable against its accepted result; - every retained Contract ID against its provider implementation, every in-scope consumer, conformance/integrat