# Claude QA Coverage — <Project>

```
Status: Current
Owner: <who maintains this>
Last reviewed: <YYYY-MM-DD>
Governs: what each QA pass actually reached
Review trigger: Any QA round run
```

> Pass by pass, what was reached and what was not. The point of this file is the
> **Blocked** rows: a pass left out of a report reads exactly like a pass that
> succeeded, and that is how untested code ships believing it was tested.

## Round <N> — <YYYY-MM-DD> at `<sha>`

| Pass | Result | Notes |
| --- | --- | --- |
| A — First run | Pass | <what was observed> |
| B — Core flow | Pass | <> |
| C — Failure paths | Partial | <which failures were simulated, which were not> |
| D — Persistence | Pass | <> |
| E — End of loop | **Blocked** | <what blocks it, and the issue number> |
| F — Accessibility | Not run | <why, and when it will be> |
| G — Performance | Pass | <the numbers, not "felt fine"> |
| H — Authorization and abuse | Not run | <which of the six cases were exercised, and as which user> |

## Standing gaps

<Things no round has ever covered, carried forward until they are. This list
existing is not a failure; it not existing while the gaps do is.>

- <gap, and what it would take to close>