statuslisted

# Orchestration Status The user wants to see the current state of orchestration. Check the following and report: ## Status Check Protocol 0. **Check degraded journal**: Read the last ≤20 lines of `.orchestray/state/degraded.jsonl` (if present). If any entry has a `ts` value within the last 24 hours, emit a one-liner **above** the rest of the status report: `> [degraded] {N} silent fallback(s) in last 24h — run /orchestray:doctor for details` where N is the count of entries newer than 24 h. Skip this step silently if the file is absent or unreadable. 1. **Check for active orchestration**: Read `.orchestray/current-task.json` if it exists. - If it exists: Report the task description, status, agents spawned, agents completed, and any pending work. - If it does not exist: Report "No active orchestration." 2. **Check state directory**: If `.orchestray/state/` directory exists, read `.orchestray/state/orchestration.md` for richer status details. This provides more information than `current-task.json` alone. - Read `orchestration.md` YAML frontmatter for: `id`, `task`, `status`, `complexity_score`, `complexity_level`, `delegation_pattern`, `current_phase`, `completed_tasks`, `total_tasks`. - Read all files in `.orchestray/state/tasks/` and parse their YAML frontmatter to build a per-task status table. - Read all files in `.orchestray/state/agents/` and parse their YAML frontmatter to show per-agent run status. 3. **Check