orchestration-envelope

# Machine envelope (internal contract) The **envelope** is one fenced `json` block, the **absolute last output** of a turn, that lets an external orchestrator route on the outcome. **Who emits it** (since feature 10 — see `docs/workflow/MIGRATION.md`): - **`workflow-status` — always**, as part of its own contract (emitting the envelope *is* the sensor's function). - **Every other skill — only when a driver asks for it**, by injecting the canonical system-prompt snippet below into the headless invocation. In an interactive/human session, no skill prints an envelope and none should be expected. - Internal skills (the review pack, the planning steps, this one) never emit it in any mode: they return their fixed completion reports to the composing caller; at most one envelope exists per turn, for the whole turn. **Parse contract for orchestrators:** take the **last fenced ```json block** of the final assistant message. Exactly one envelope per turn; parse failure → the repair loop below. ## Schema (all top-level keys ALWAYS present — use null / [] / 0 when n/a) ```json { "skill": "<emitting skill name>", "state": "OK | CONTINUE | READY_FOR_REVIEW | READY_FOR_AUDIT | MERGE_READY | MERGED | NEEDS_FIXES | BLOCKED | NEEDS_INPUT | FAILED | HALT", "summary": "<one plain-text sentence: what happened this turn>", "unit": {"type": "feature | fix | docs | none", "id": "<NN-slug | N-topic | null>", "issue": null, "branch": "<branch | null>"}, "phase": {"current": "...