coord-orchestratelisted

# Coordination Orchestrate <!-- delivery-flow/1 --> This is the generic authored delivery flow. A tracked or installed host copy is a projection, not a second procedure. Host and repository instructions retain precedence for safety, verification, review and merge authority. This skill is caller guidance; it adds no Edda scheduler, lock, approval service or runtime role enforcement. ## Modes This skill is the strong planning and exception path. Runtime advancement is a separate, smaller loop with its own skill. | Mode | Runtime | Product surface | |---|---|---| | `prepare` | strong planner | Author/validate a `ControlManifestInputV1` and compile it into a sealed `ControlManifestV1` with `edda control compile <file> --json` | | `run` | Flash runtime | Advance the sealed control with `coord-run` through `edda control status`/`next`/`apply` | | `exception` | strong planner | `edda control adjudicate <id> --state-version <n> --decision <file> --json` clears `needs_decision`; `edda control authorize-merge <id> ... --json` binds a separate merge capability | ### Prepare mode The strong planner owns the goal, decomposition, DAG, scope, routes and the review charter, and encodes them in the `ControlManifestInputV1` that compiles to a `ControlManifestV1`. Validate the input schematically before compiling; a refused compile is a refusal, not a reason to weaken the manifest. Compile is the strong path and carries no merge authority: it atomically accepts the brief inputs and one m