recover-sessionlisted

# /recover-session — bring a dead session back A session's full context lives in its transcript on disk; `claude --resume <uuid>` (run from the right cwd) replays it. This skill finds the UUID + cwd and hands the user the resume command. **Recovery is standalone** — it restores the session's context/brain, NOT its live role in an orca run. A resurrected orca agent comes back as a solo session the user talks to directly; it can still finish its task, commit, and write its sentinel, but the orchestrator's spawn linkage is gone. ## Fast path — orca run roster Orca's orchestrator and every spawned agent self-register `{name, session_id, cwd, worktree, timestamp}` to `<project-root>/.claude/status/roster.jsonl` as their first action. Look the session up there via the helper next to this skill: ```bash ~/.claude/skills/recover-session/recover.sh list # from the project root ~/.claude/skills/recover-session/recover.sh show <name> # prints the resume command ``` The helper derives the resume cwd from the transcript's own `cwd` field — authoritative, because a session's launch cwd can differ from the worktree it works in. ## Fallback — transcript grep (no roster, or session_id "unknown") 1. `grep -rl "<keyword>" ~/.claude/projects/*/*.jsonl` — use a distinguishing keyword (task name, a unique phrase from the work), inspect newest first (`ls -t`). 2. The session you want is the one whose **first user message is the task prompt naming the agent** (for orca a