coverage

# Coverage Report You are computing and reporting code coverage for the active track or a specific module. This complements the TDD workflow — TDD is the process (write test, implement, refactor), coverage is the measurement (how much code do those tests exercise). ## Red Flags - STOP if you're: - Reporting coverage without actually running the coverage tool - Making up coverage percentages - Skipping uncovered line analysis - Not presenting the report for developer approval - Treating this as a replacement for TDD (it's not — TDD stays in `/draft:implement`) --- ## Step 1: Load Context 1. Read `draft/tech-stack.md` for test framework and language info 2. Find active track from `draft/tracks.md` 3. If track has `architecture.md` (track-level) or project has `.ai-context.md`, identify current module for scoping 4. Look for `coverage_target` in `draft/workflow.md`. Check for per-module targets first (see Per-Module Coverage Enforcement below); if absent, default to 95%. 5. Check if `draft/tracks/<id>/bughunt-report-latest.md` (track scope) or `draft/bughunt-report-latest.md` (project scope) exists for cross-referencing (see Coverage-Bughunt Cross-Reference below) If no active track and no argument provided: - Tell user: "No active track. Provide a path or track ID, or run `/draft:new-track` first." ## Step 2: Detect Coverage Tool **Preferred:** use the deterministic `detect-test-framework.sh` wrapper — it emits JSON `{languages:[{language,framework,runner_command,test_...