human-review-pack

Assemble everything a human needs to approve a PR or release — with evidence, not claims. Read-only. The pack must let a reviewer decide in minutes and must not overstate readiness.

Steps

1. Collect the diff summary — changed files/areas per stack; new endpoints/migrations/UI.
2. Pull the proof — the /verify reports and .maestro/<slug>/<stack>/last-verify.json markers per stack; the QA suite result. If proof is missing or status:"fail", say so — do not claim green.
3. Pull the reviewer findings — .maestro/<slug>/architecture-review.md and each stack's reviews/summary.md; separate what was fixed from what is deferred/accepted.
4. Assess risk & release readiness — migrations, flags, rollout/backout, data impact.
5. Write the pack and state the exact decision required.