# Specialist Review Report

## Scope

- Base ref: not provided
- Diff summary: 0 displayed / 0 suppressed / 0 merged findings
- Changed files: see evidence artifacts or scope output
- Diff lines: see scope output when provided

## Specialist Dispatch

| Specialist | Status | Reason |
| --- | --- | --- |
| api-contract | skipped | no normalized findings |
| data-migration | skipped | no normalized findings |
| maintainability | skipped | no normalized findings |
| performance | skipped | no normalized findings |
| security | skipped | no normalized findings |
| testing | skipped | no normalized findings |

## Findings

| Severity | Confidence | Specialist | Path | Summary | Recommendation |
| --- | ---: | --- | --- | --- | --- |
| none | 0.00 | none | none | No displayed specialist findings. | none |

## Red Team

- Status: not required
- Activation reason: none
- Added findings: none generated by this primitive

## Evidence Reviewed

- Input rows: 0
- Input files: 
- Validation commands: caller-provided
- Logs/artifacts: caller-provided

## Residual Risk

- Low-confidence concerns: none suppressed by threshold
- Unverified claims: specialist-authored findings only; no provider mutation performed
- Coverage gaps: validate with repo tests before delivery

## Recommended Next Step

- Decision path: caller workflow decides follow-up, merge, or close actions
- Follow-up owner: caller workflow
- Review-evidence record: optional

Note: this report distinguishes specialist review findings from merge, close, or request-followup decisions. Use `dispatch-pr-review` for those decisions.
