rescue

# rescue ## Purpose Legacy refactoring orchestrator for safely modernizing messy codebases. Rescue runs a multi-session workflow: assess damage (autopsy), build safety nets (safeguard), perform incremental surgery (surgeon), and track progress (journal). Designed to handle the chaos of real-world legacy code without breaking everything. <HARD-GATE> - Surgery MUST NOT begin until safety net is committed and tagged. - ONE module per session. NEVER refactor two coupled modules simultaneously. - Full test suite must pass before rescue is declared complete. </HARD-GATE> ## Triggers - `/rune rescue` — manual invocation on legacy project - Auto-trigger: when autopsy health score < 40/100 ## Calls (outbound) - `autopsy` (L2): Phase 0 RECON — full codebase health assessment - `safeguard` (L2): Phase 1 SAFETY NET — characterization tests and protective measures - `surgeon` (L2): Phase 2-N SURGERY — incremental refactoring (1 module per session) - `retro` (L2): post-rescue retrospective — capture lessons learned - `journal` (L3): state tracking across rescue sessions - `plan` (L2): create refactoring plan based on autopsy findings - `review` (L2): verify each surgery phase - `session-bridge` (L3): save rescue state between sessions - `onboard` (L2): generate context for unfamiliar legacy project - `dependency-doctor` (L3): audit dependencies in legacy project - `context-pack` (L3): create structured handoff briefings before spawning subagents - `neural-memory` | Phase start + pha...