codebase-analysislisted

# Codebase Analysis Run a broad aidd-oriented codebase analysis across architecture, performance, security, metadata health, and technical debt. ## Usage ``` codebase-analysis [app] ``` ## Scope (analysis only) This is a read-only analysis. It observes and reports; it does not change the project. - Do NOT edit source files or config (including `tsconfig.json`, `package.json`, lint config). - Write only under `.aidd/audit-reports/` (the report) and `.aidd/CHANGELOG.md` (the summary). - Do NOT `git add` or `git commit`; leave the deliverables as workspace artifacts for the user. - Run build, lint, and tests to observe status only. Never apply a fix to make a gate pass; a failing gate is a finding to report, not a task to resolve. ## Instructions 1. **Comprehensive context mapping**: - Analyze all architectural patterns and their relationships - Map data flow across the entire application - Identify integration points and dependencies - Assess type safety across the codebase - Identify performance bottlenecks and optimization opportunities - Review security patterns and potential vulnerabilities - Evaluate code quality metrics and technical debt - Map reusable components and their usage patterns 2. **Historical evolution analysis**: - Review git history for architectural decisions and outcomes - Identify bug patterns and resolution strategies - Assess code quality trends over time - Note technical debt accumulation and r