relay-fleetlisted

## Inputs - Env: optional `RELAY_SKILL_ROOT` defaults to `skills`. - Files: leaves JSON passed by `--leaves-file`, child prompt/rubric/Done Criteria files, immutable cohorts under `~/.relay/fleets/`, and child runs under `~/.relay/runs/`. - Sibling scripts: `${RELAY_SKILL_ROOT:-skills}/relay-fleet/scripts/relay-fleet.js`, `${RELAY_SKILL_ROOT:-skills}/relay-dispatch/scripts/dispatch.js`, `${RELAY_SKILL_ROOT:-skills}/relay-review/scripts/review-runner.js`, `${RELAY_SKILL_ROOT:-skills}/relay-merge/scripts/finalize-run.js`. # relay-fleet ## Use when - Driving already planned relay leaves through fan-out, review/redispatch, serial merge, and close - Re-running the same fleet command after a crashed or killed session - Continuing an immutable cohort from its current child-run facts - Printing read-only aggregate status for a fleet ## Do not use when - Decomposing raw or ambiguous requests into leaves — use `relay-ready` - Authoring per-leaf rubrics or dispatch prompts — use `relay-plan` - Dispatching a single task or run — use `relay-dispatch` - Reviewing one standalone child PR — use `relay-review` Run multi-leaf orchestration after `relay-ready` and `relay-plan` have already produced leaf artifacts. A fleet stores only one immutable cohort. Status is derived afresh from Relay `run.json` records and canonical `inspect` results; it never owns child state, retry history, or a cache. Retired run artifacts are not read. Design rationale, rejected alternatives, non-goals, and th