This is a review task. Write your review to:
  {report_path}

Your prompt already includes changed files, diffstat, and relevant diff/context excerpts. Base your review on that provided context and avoid using git discovery commands.

Project-specific guidance:
- Follow repository instructions (for example AGENTS.md, REVIEW.md, project docs, and configured verification commands when available).
- Keep this review stack-agnostic. If project verification instructions are missing, state that explicitly in assumptions/risks.

Output format contract (use this exact section order and exact headings):
1. ## Summary
2. ## Must-Fix
3. ## Suggestions
4. ## Questions / Assumptions
5. ## Verdict

Do not rename, omit, or reorder these sections.

Section requirements:
- ## Summary
  - Provide 3-5 bullets summarizing the review.
- ## Must-Fix
  - If there are no blocking issues, write exactly: None.
  - Otherwise list issues ordered by severity with headings:
    - ### M1
    - ### M2
    - ...
  - Each must-fix item must include these labeled fields:
    - Evidence:
    - Impact:
    - Required fix:
    - Required tests:
- ## Suggestions
  - If there are no non-blocking suggestions, write exactly: None.
  - Otherwise list suggestions with headings:
    - ### S1
    - ### S2
    - ...
  - Each suggestion item must include:
    - Evidence: (optional but encouraged)
    - Suggestion:
    - Why it helps:
- ## Questions / Assumptions
  - If there are none, write exactly: None.
  - Otherwise provide bullets.
- ## Verdict
  - Include a brief rationale.
  - Final line must be exactly one of:
    - Verdict: APPROVED
    - Verdict: CHANGES_REQUESTED
    - Verdict: NEEDS_DISCUSSION

Blocking discipline:
- Request changes only for concrete, actionable blockers.
- For each blocker, give a clear closure condition so an improve task can resolve all blockers in one pass.

Historical review files may use older formats; keep this output contract for all new reviews.
