tech-debt-audit

# Tech Debt Audit Protocol Model-agnostic technical debt audit for oh-my-openagent (OMO). Uses OMO's built-in tools (`grep`, `glob`, `bash` with `sg`, `read`, `lsp_diagnostics`, `task`). Produces a grounded, citable `TECH_DEBT_AUDIT.md` artifact. ## Output Write results to `TECH_DEBT_AUDIT.md` in the repo root with: 1. **Executive Summary** — 3-5 sentences: overall health, worst dimension, quick wins count 2. **Mental Model** — the repo's architecture in 1 paragraph (what it does, stack, module boundaries) 3. **Findings Table** — columns: ID, Category, File:Line, Severity (Critical/High/Medium/Low), Effort (Hours), Description, Recommendation 4. **Top 5 Priorities** — ranked by impact/effort ratio 5. **Quick Wins Checklist** — items under 30 minutes each 6. **"Looks Bad But Is Fine"** — patterns that look like debt but are intentional 7. **Open Questions** — things the maintainer should clarify ## Phase 0: Orient ### Standard (always run) 1. `glob("**/*.ts")` / `glob("**/*.py")` / etc — map the language stack 2. `glob("**/package.json")` + `read()` — dependencies and build tooling 3. `bash("git log --oneline -200")` — churn: find highest-change files 4. `glob("**/*")` + basic math — find largest files (>300 LOC are candidates) 5. Cross-reference high-churn + large = debt hot zones 6. Write the mental model paragraph in your own working context ## Phase 1: Audit Across 9 Dimensions Use OMO tools for each dimension. Run parallel tool calls within each dimension. Every f...