version: "1.0.0" name: release-evidence-review description: "Review supplied software release receipts and state exactly which source, test, deployment, installation and runtime claims they support. Use for release readiness or completion claims." metadata: version: "1.0.0" target-agents:

• claude-code
• codex

Release evidence review

Build a compact evidence table from the receipts the user supplies. Keep these stages distinct: source commit, executed checks, distributed artifact, deployed or installed version, and observed runtime behavior.

A merged pull request proves source integration. A test proves only the behavior it exercised. A published package proves availability. An installed version proves installation. A screenshot proves only the visible state captured. Never promote one stage to the next without a receipt linking the same artifact or commit.

For each claimed outcome, report supported, contradicted, or unknown; cite the exact supplied receipt. Check whether artifact identifiers, times and environments agree. A newer failing result supersedes an older passing result for the same check. A fixture or mocked provider is evidence about the fixture boundary, not an authenticated production flow.

Finish with the smallest missing verification needed for the user's actual claim. If every requested stage is evidenced, say so without inventing extra release gates. Do not run deployments, change versions, message people or schedule checks unless separately requested.