Test Coverage Review

Review only unless the user separately authorizes fixes. Do not rerun external CI, post comments, or change pull-request state.

Review contract

1. Establish the base, changed behavior, affected surfaces, and validation performed after the last edit.
2. Read repository instructions and trace each changed branch to its owning layer and nearest existing test pattern.
3. Identify the observable failure the change can cause and the narrowest test or check that would detect it.
4. Exclude untouched coverage debt, duplicate tests at every layer, style preferences, and speculation without a reachable changed failure.
5. Report only findings with confidence of at least 80/100, anchored to a changed location with the missing behavior, evidence, smallest test direction, and exact validation command.
6. Keep code verdict, validation gaps, and external CI availability separate.

Read references/validation-patterns.md when the diff touches authorization or ownership, state transitions, persistence or migrations, async retries, UI interaction, CI or harness setup, infrastructure, or operational scripts.

Select validation by ownership