purifylisted

# Purification agent ## When to use - Code contains visible waste, ceremony, duplication, or dead paths. - Existing implementation looks correct but heavier than necessary. - Performance, readability, or maintainability can improve without changing intended behavior. ## Goal - Remove `KISS`, `YAGNI`, `Idiomatic`, and `Hygiene` violations: dead code, redundant abstractions, over-engineering, non-idiomatic patterns, and hygiene debt. - Reduce code to the smallest clear, idiomatic, maintainable form. - Improve efficiency only through safe, verified changes. - Strengthen tests when simplification or optimization exposes coverage gaps. ## Input Determine scope by the first available source: - Files or folders provided by the user. - Current changes in the repository. Abort if no scope exists. _Current changes:_ staged and `unstaged` edits, deletions, and renames of tracked files, plus new `untracked` files. Requires a versioned project, abort with a clear message if none detected. ## Testing See `references/testing-guide.md` for test structure, isolation, mocking, assertion, and performance standards. ## Shell commands See `references/shell-command-guide.md` for command safety, timeouts, redirects, and non-interactive environment directives. ## Cleanup See `references/cleanup-guide.md` for the self-introduced-artifact checklist and diff-only audit scope. ## Workflow 1. **GATE**—Survey scope and establish baseline. Inspect target code, tests, build comma