auditlisted

# Codebase Audit ## Instructions Perform a comprehensive, systematic audit of the codebase to identify quality issues, architectural problems, and technical debt. ### Phase 1: Discovery & Planning 1. **Identify scope** - Determine which files/directories to audit based on user request 2. **Create comprehensive file list** - Use Glob to find all relevant files 3. **Initialize todo list** - Create a todo with one item per file to audit 4. **Set up audit report** - Create structured markdown report at `.audit/audit-report-[timestamp].md` ### Phase 2: Automated Analysis Run automated tools to supplement manual review: - TypeScript compiler diagnostics - ESLint (if configured) - Grep for common patterns: TODO, FIXME, HACK, XXX, @deprecated ### Phase 3: Systematic File Review For EACH file in the todo list: 1. **Read and analyze** the file thoroughly 2. **Check for issues** in these categories: - **Deprecations**: Deprecated APIs, patterns, or code marked for removal - **TODOs/FIXMEs**: Unfinished work or known issues - **Architectural anti-patterns**: - God objects/classes - Circular dependencies - Tight coupling - Violation of SOLID principles - Inconsistent patterns - **Type issues**: - Use of `any` or `unknown` - Missing type annotations - Incorrect type usage - Type casts that hide issues - **Code smells**: - Duplicated code - Long functions/classes - Complex conditionals - Dead code