Feedback request: review packet for AI-written PRs

[camirian]

Hi - I am validating a narrow PR review evidence verification workflow this week. This project is relevant because OpenSpec focuses on spec-driven development for AI coding assistants, where review evidence and acceptance criteria are central.

The workflow: for one AI-written PR or small release candidate, produce a 24-48 hour reviewer packet with changed-file summary, available checks, missing evidence, risk flags, reviewer questions, and possible merge blockers. It does not approve code, replace maintainers, run private tests, or claim security/compliance sign-off.

I am trying to learn whether this would reduce review effort or just add noise around AI-assisted code changes.

Useful feedback would be blunt answers to any of these:

• What evidence would make this packet useful before a human review?
• What would make it redundant with existing tooling?
• Is public PR metadata plus bounded diff excerpts enough for a first pass?
• If you had one AI-written PR this week, would this be worth a useful addition or redundant?

Public demo context: https://github.com/camirian/agent-evidence-recorder

Boundary: public PR metadata only; no private repos, secrets, customer data, compliance/security approval, or merge authority.