Audit Dead Code

Audit reachability before deleting anything. Build a proof chain from live entrypoint to candidate, then apply the smallest safe removal.

Follow this workflow

1. Map the codebase entrypoints, public surfaces, and dynamic loading surfaces in scope.
2. Search for references from public surfaces inward, not just from the candidate itself.
3. Classify each candidate as unused export, unreachable code, orphaned file, stale feature flag, dead registration, or legacy compatibility path.
4. Build a proof chain with code search, config or registry checks, framework conventions, and typecheck, build, or tests where available.
5. Prioritize findings as P1 through P4.
6. Auto-fix only local, low-risk removals. Leave broader deletions as findings with a concrete removal plan.

Map live entrypoints first

Do not start deleting from leaf files without understanding how code can be reached.

Inspect the relevant equivalents of: