featurelisted

# Orchestray Feature Quarantine Management The user wants to manage feature demand-gate quarantine state. ## Protocol ### Step 1 — Parse subcommand Parse `$ARGUMENTS`. The first whitespace-separated token is the subcommand. | Subcommand | Description | |------------|-------------| | `wake` | Wake a quarantined feature (session or 30-day pinned) | | `status` | Show quarantine state and active wakes | | `list` | Alias for `status` | If the subcommand is empty, treat it as `status` (default). If the subcommand is not in the table above: - Emit: "Unknown subcommand '<name>'. Available: wake, status, list." - Stop. --- ### Step 2 — `wake` branch Syntax: `wake [--persist] <name>` Parse the remaining tokens after `wake`. If `--persist` is present (anywhere in the remaining tokens), this is a 30-day pinned wake; otherwise it is a session-local wake. The feature name `<name>` is the gate slug (e.g., `pattern_extraction`, `archetype_cache`). Invoke via Bash: ``` node bin/feature-wake.js [--persist] <name> ``` Display the output as-is. **Session wake (no --persist):** - Adds `<name>` to `.orchestray/state/feature-wake-session.json`. - Emits a `feature_wake` audit event with `scope: "session"`, `caller: "cli"`. - The gate is treated as enabled for the remainder of this session (overrides quarantine_candidates). - Session wake is cleared on session end (file is session-scoped; a fresh session starts with a clean file). **30-day pinned wake (with --persist):** - A