session-recoverylisted

# Session Recovery ## Purpose Reconstruct enough context to continue work after a session interrupt: a crashed terminal, a fresh `claude` invocation, a long-running task that lost track of its own state. The skill is a guided walk through the persistent state YakOS maintains, in priority order. ## Scope Operates on the current project's `~/agent-control/<project>/` and `~/.claude/projects/<encoded>/`. NOT in scope: reconstructing what was in volatile memory only (e.g. an in-flight tool call's arguments). ## Automated pass Walks state in priority order: 1. **Read `work/current/decisions.md`** if present — this is the highest-signal recap of what was decided. 2. **Read `work/current/plan.md`** for the current decomposition. 3. **Read `work/current/status.md`** for the task list mirror. 4. **Read `work/current/contracts.md`** for any inter-team contracts that aren't yet code. 5. **Tail `work/current/logs/*.ndjson`** — recent hook outcomes show what the team was doing in the last few minutes. 6. **Tail `work/current/messages.ndjson`** — recent peer DMs (per Phase 1.7's mailbox-mirror). 7. **Read `~/.claude/projects/<encoded>/MEMORY.md`** index — the cross-session memory the lead has accumulated. 8. **Read every `feedback_*.md` file** referenced from MEMORY.md. The index alone is insufficient: feedback memories encode durable operating rules (e.g. "always delegate coding work in parallel", "write session checkpoints every milestone"), and a session t