run-tasklisted

# Run confirmed task cards <HARD-GATE>Every dispatched task must exist in an independently reviewed and primary-orchestrator-accepted `Task.md`, belong to the confirmed `target_milestone_id` execution set, and have valid Requirement plus Design-stage authority, including the applicable `Contract.md` anchor when one exists. A task is ready only when its Task prerequisites are closed on the shared baseline and any declared shared-resource constraint is available. If implementation changes upstream meaning, stop only its impact cone and revise that authority.</HARD-GATE> The primary orchestrator owns scheduling, adjudication, shared state, integration, Task status, and per-card execution documents. It may be the Coder for one task only when no useful implementation work can run in parallel with orchestration; it cannot replace the independent Reviewer or any risk-triggered Verifier. ## 1. Materialize execution documents Before the first Coder dispatch, the primary orchestrator creates exactly two files for each confirmed task selected for this run: 1. `execution/<card_id>/Card.md` first. It is normative and contains the stable task execution contract: exact Task/Requirement/Design and applicable interface-Contract anchors, outcome, completion criterion, TDD contract, and `execution_log: [Log.md](Log.md)`. Add scope exclusions or an allowed path/write set only when they materially bound a delegated writer. Add conflict domains or runtime locks only for a real sha