improving-testslisted

# Test Improvement Improve tests so they catch real behavior regressions without blocking safe code changes. Coverage is a signal, not the goal. ## Role-gated action Detect capability from tools: - Write-capable role: inspect tests, apply changes, and run verification. - Read-only role: inspect supplied files/output and emit changes in the Proposed Changes contract. Apply nothing; run nothing. - Missing key tool or permission: stop with Blocked and ask for the exact artifact, access, or approval needed. Use an interactive question tool when available for mode selection, missing scope, missing framework approval, or unsafe test-stack choices. ## Route elsewhere Do not use this for: - production bug fixes → `fixing-code` - production-code refactors → `refactoring-code` - non-test code review → `reviewing-code` - new feature implementation unless the user asked for TDD - browser-only UI investigation without a test-improvement goal → `browser-automation` ## References Detect languages from files in scope and read only the matching reference: - Go → `references/go.md` - Python → `references/python.md` - TypeScript → `references/typescript.md` - Web → `references/web.md` Use generic rules only for unsupported languages. ## Modes - `review`: find weak, duplicate, brittle, missing, slow, or flaky tests - `refactor`: simplify tests without changing covered behavior - `coverage`: add tests for uncovered business behavior or error paths - `tdd`: one red-green-refactor sli