# `<capitalize the first word; do not reuse the commit subject; describe the primary issue or fix summary>`

## Summary

`<one paragraph summary of the fix and scope>`

## Problem

- Expected: `<what should happen>`
- Actual: `<what happens today>`
- Impact: `<user-facing impact / severity>`

## Reproduction

1. `<step-by-step commands or clicks>`
2. `<minimal repro script/command when available>`

- Expected result: `<what should happen>`
- Actual result: `<what happens today>`

## Issues Found

Severity: critical | high | medium | low Confidence: high | medium | low Status: open | fixed | deferred | needs-info

|ID|Severity|Confidence|Area|Summary|Evidence|Status|
|---|---|---|---|---|---|---|
|`PR-<number>-BUG-01`|high|medium|`module/path`|`one-line summary`|`file:line or repro`|fixed|

## Fix Approach

- `<key changes>`

## Test-First Evidence

- Change classification: `<bug fix | behavior change | docs/config/generated/visual-only waiver>`
- Failing test before fix: `<command, exit code, failing test file/name, concise failure summary; or N/A with waiver>`
- Final validation: `<command and result after fix>`
- Waiver reason: `<only when failing-test evidence was not practical>`

## Testing

- `<command>` (pass)
- not run (reason)

## Risk / Notes

- `<optional>`
