statelisted

# Orchestray State Management The user wants to inspect or manage Orchestray runtime state. ## Protocol ### Step 1 — Parse subcommand Parse `$ARGUMENTS`. The first whitespace-separated token is the subcommand. | Subcommand | Status | |------------|--------| | `peek` | Implemented — read-only state inspection | | `gc` | Implemented — archive or discard leaked state | | `pause` | Implemented — pause or resume an active orchestration (v2.0.18 W7) | | `cancel` | Implemented — request cancellation of an active orchestration (v2.0.18 W7) | If the subcommand is empty, treat it as `peek` (default). If the subcommand is not in the table above: - Emit: "Unknown subcommand '<name>'. Available: peek, gc, pause, cancel." - Stop. <!-- W7-INSERT: add `pause` and `cancel` branches here --> --- ### Step 2 — `pause` branch (pause or resume) For the `pause` subcommand, invoke `bin/state-pause.js` with any flags passed after the subcommand. Supported flags: - `--resume` — remove the pause sentinel, resuming the orchestration. Idempotent. - `--reason=<msg>` — optional human-readable reason stored in the sentinel. **First call (no `--resume`):** creates `.orchestray/state/pause.sentinel` with the current `orchestration_id`, optional reason, and `paused_at` timestamp. Emits a `state_pause_set` audit event. Idempotent — if the sentinel already exists, reports "already paused" and exits without changes. **With `--resume`:** deletes the sentinel if present, emits `state_pa