shipkit-orchestratelisted

# shipkit-orchestrate — Core Automation Engine **Purpose**: One reusable orchestration loop that every phase skill calls, so Shipkit has exactly **one way to drive work to completion** instead of a separate hand-rolled loop per phase. It dispatches units, **reconciles their output against ground truth** (never self-reports), re-dispatches the gaps, integrates, and stops at an agreed bar. **Read first**: `install/shared/references/core-automation.md` — the contract (substrate choice, the worktree finding, partition, the ledger, ground-truth reconciliation, integration policy, the parallel-build lifecycle, deterministic-mechanism-vs-judgment). This SKILL.md is the entry point; the contract is the machinery. **Runs inline in the main session.** The engine launches Workflow fan-outs and drives git + `AskUserQuestion`, all of which require the main session — it is *not* a forked orchestrator. A phase skill that needs parallel fan-out hands its plan **up** to the engine (which the main session is running), and the engine launches. --- ## Calling interface A caller invokes the engine with four things: | Input | What it is | |-------|------------| | **steps** | the ordered / parallel units to drive — each a `{ skill or work, artifact }` pair (what to run, what it must produce) | | **bar** | the **ground-truth completion criteria** per step — the named `.shipkit/` artifacts that must exist + any check (tests green, review passed). This is what "done" means; the caller must stat