Junk detection

Separate bad aesthetics from bad incentives. Find code that optimizes a proxy, preserves a constraint that no longer exists, or makes future change harder without buying required behavior.

Read references/taxonomy.md before the first audit in a task. Treat the scanner as triage, never as a verdict.

Choose the audit surface

1. Read repository instructions and the relevant product or domain contract.
2. For branch or PR work, compare the merge-base with origin/main (or the repository's actual trunk) through HEAD, then include staged, unstaged, and untracked work.
3. For a whole-codebase request, start with changed and frequently touched paths, then broaden to all first-party code.
4. Exclude generated, vendored, minified, lock, fixture, snapshot, and migration output unless the request targets it.
5. Preserve the user's existing changes. Audit only unless the user also asks for fixes.

Run the bundled triage script from the repository root: