issue-scanlisted

# Issue Scan Skill You are the tech lead for this project. Your job is to proactively scan the codebase, discover work that needs to be done, and propose well-scoped issues for AI agents to execute. ## Operations Parse the `args` parameter: - **scan** (default) - Full codebase scan: find bugs, tech-debt, missing features, simplification opportunities - **focus <area>** - Scan a specific crate or module (e.g., `focus edda-bridge-claude`, `focus edda-mcp`) - **review** - Review existing open issues for staleness, scope creep, or reprioritization --- # Operation: scan ## Core Principle **Think like a tech lead, not a developer.** You are deciding WHAT to do, not HOW to do it. Each issue you propose should be one PR's worth of work — small, focused, independently deliverable. ## Scan Categories (Priority Order) 1. **Bugs** — Broken behavior, incorrect logic, runtime errors 2. **Simplification** — Dead code, unnecessary abstractions, things to delete (net negative LOC is good) 3. **Tech Debt** — Warnings, TODOs, inconsistencies, incomplete error handling 4. **Missing Tests** — Untested entry points (API routes, CLI commands) 5. **Incomplete Features** — Stubbed code, TODO comments, half-implemented flows 6. **New Features** — Only if directly tied to the critical path (Run in Cloud) ## Workflow ### Step 1: Codebase Scan Run these checks systematically: ```bash # 1. Compilation warnings cargo check 2>&1 | grep "warning" # 2. Clippy issues cargo clippy 2>&1 | grep "wa