showdar-recoverlisted

# Showdar Recover ## Purpose - Recover context after session interruption, compaction, agent failure, crash, or handoff. - Distinguish completed-and-proven work from partial, broken, unrelated, and merely claimed work. - Prevent duplicate edits or accidental overwrite of user/uncommitted state. - Resume from the smallest verified checkpoint. - Read `references/interrupted-session.md` and `references/partial-implementation.md` before editing anything. ## When to use - Agent/task stopped mid-run. - New session needs to continue previous repository work. - Context was compacted and exact progress is uncertain. - Merge/rebase/conflict or failed automation left ambiguous partial state. - User asks “where were we?”, “continue from current state”, or “recover this task”. ## When not to use - Clean new task with no prior partial work. - Normal code review or architecture understanding. - Do not infer original goal from unrelated git history when user/task context is available. - Do not auto-resolve conflicts before understanding both sides. ## Inputs and assumptions - Repository/worktree state and any task/spec/plan/chat summary available. - Git history/status/diff are evidence but may contain unrelated user changes. - Previous agent narration is a hint, not proof. - `scripts/inspect-state.mjs` performs read-only git-state collection. - Fresh tests/builds are needed before classifying a change as proven complete. ## Non-negotiable rules - Do not edit files until current sta