# Specialist Review Report

## Scope

- Base ref: not provided
- Diff summary: 2 displayed / 1 suppressed / 3 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 | selected | 1 merged finding(s) |
| performance | selected | 1 merged finding(s) |
| security | skipped | no normalized findings |
| testing | selected | 1 merged finding(s) |

## Findings

| Severity | Confidence | Specialist | Path | Summary | Recommendation |
| --- | ---: | --- | --- | --- | --- |
| high | 0.85 | testing | src/lib.rs:42 | Missing test for new branch | Add a unit test exercising the new branch. |
| medium | 0.72 | maintainability | src/util.rs:10 | Function is too long | Split the helper into smaller functions. |

## Red Team

- Status: required
- Activation reason: forced via flag
- Added findings: none generated by this primitive

## Evidence Reviewed

- Input rows: 3
- Input files: findings-a.jsonl, findings-b.jsonl
- Validation commands: caller-provided
- Logs/artifacts: caller-provided

## Residual Risk

- low (0.45) src/main.rs:5: Allocation inside loop
- 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.
