code-maintenance-auditlisted

# Code Maintenance Audit Avoid code tunnel vision after implementation. Treat every code change as a chance to clean up directly affected dead code, stale leftovers, and needless duplication without turning the task into an uncontrolled refactor. ## Operating Rule Before claiming a code task is done, perform a maintenance sweep over the changed files and their immediate dependency neighborhood: 1. Scope pass: list the changed files, touched symbols, and direct callers/callees or imports/exports. 2. Dead-code pass: remove code made unused, unreachable, or obsolete by the current change when it is safe to prove. 3. Consolidation pass: look for near-duplicate components, classes, functions, branches, or test fixtures adjacent to the work. 4. Proof pass: run the existing relevant typecheck, lint, unit tests, build, or repository-specific verification. Do not expand into broad architecture work unless the user requested it or the low-risk cleanup is clearly inside the touched surface. Walk the full target inventory in `$PLUGIN_ROOT/references/maintenance-checklist.md`: unused symbols, replaced branches/flags/adapters, near-duplicate implementations, dead files after renames, debug leftovers, and repeated logic expressible through an existing local helper. ## Evidence Standard - Use `rg` first for symbol references, imports, string identifiers, routes, feature flags, config keys, and test names. - Prefer repo-native tools when present: compiler/typecheck, linter, dead-code