spec-bugfix-verify

# /spec-bugfix-verify - Bugfix Verification Phase **Phase 3 (bugfix).** Lightweight verification: run tests, quality checks, confirm fix works. **Input:** Bugfix plan with `Status: COMPLETE` **Output:** Plan → VERIFIED (success) or loop back to implementation (failure) **Why no sub-agents:** The regression test proves the fix works. The full test suite proves nothing else broke. Sub-agents would re-verify what tests already prove. --- ## Critical Constraints - **NO review sub-agents** — tests prove correctness for bugfixes - **NO stopping** — everything automatic. Never ask "Should I fix these?" - **Fix ALL issues automatically** — no permission needed - **Plan file is source of truth** — re-read after auto-compaction --- ## Step 3.1: Run Full Test Suite Run all tests. Fix any failures immediately. Re-run until green. ## Step 3.2: Verify the Fix 1. **Read the plan's regression test** (from Task 1) 2. **Run it specifically:** `uv run pytest <test-path>::<test-name> -q` 3. Must PASS — if not, fix is incomplete, fix immediately 4. **Scope check:** Read changed files, confirm changes match plan scope. Flag unplanned changes. ## Step 3.3: Quality Checks 1. **Type checker** — zero new errors 2. **Linter** — errors are blockers, fix immediately 3. **Build** (if applicable) — must succeed 4. **Performance audit** — For changed files on hot paths: expensive uncached work? Heavy dependency imports with lighter alternatives? Repeated invocations redoing work when input hasn...