clean-project-codelisted

# Clean Project Code Read the repository instructions first. Prefer `AGENTS.md`, the nearest relevant `CODING_STYLE.md`, and the active Prettier config before making changes. Keep the cleanup conservative. Delete only code that is clearly unused and safe to remove. When safety is ambiguous, leave the code in place and report it as a cleanup candidate. ## Workflow 1. Read repo rules. Locate and read `AGENTS.md`, `CODING_STYLE.md`, and `prettier.config.*` or `.prettierrc*` before editing. If the user names an exact path, use that file as the source of truth. 2. Define safe scope. Do not change behavior or public APIs. Do not rewrite large areas only for style. Do not edit generated files unless you also update the source that generates them. 3. Identify provably safe cleanup targets. Prefer removing: - unused imports - unused local variables and private helpers - unused types and interfaces - unreachable branches - obsolete files that are provably unreferenced - compatibility shims or dead helpers that have no live call sites 4. Prove before deleting. Use fast search tools such as `rg` to verify references. Check exports, dynamic imports, generated references, route registration, configuration wiring, and framework conventions before deleting a file or symbol. 5. Keep uncertain cases. If code looks unused but safety is not clear, keep it and report it separately. Favor false negatives over unsafe deletions. 6. Audit redundancy candidates across the project. List catalo