Review Reports

This route retains one immutable report for every completed $review-phase run. The index and route metadata are navigation envelope; report files are evidence and remain unchanged after creation.

Report Identity

Reports use:

<review-scope-slug>-<UTC>-<snapshot12>-review-report.md

review-scope-slug comes from stable review lineage. Each report records lineage and run IDs, accepted bounds, normalized target, frozen snapshot hash, governing-source hashes, mode, lens outcomes, stable findings, routing, and readonly validation. Delivery reports also carry review and preceding repair ordinals. Standalone reports mark delivery-only fields not applicable.

Required Lens Outcomes

Each report has distinct outcomes for:

1. Standards
2. Skill adherence and scoped skills
3. Architecture
4. Simplify
5. Spec

Standards and Spec remain separate axes. Presentation follows the order above; every independent lens inspects the same frozen snapshot in parallel. One $autoreview run supplies advisory candidates, and parent verification decides which candidates become findings.

Skill-adherence review checks each IMPLEMENTATION-NOTES.md evidence claim against the frozen changed artifacts, including not_applicable claims. Missing, extra, or contradicted evidence is a finding.

Retention And Authority

A complete local report enters report_retention_pending without consuming a delivery review. The designated writer commits only the report, navigation, and wiki-log envelope, then verifies that an approved retained ref contains the report commit. Delivery uses its current branch or an approved retained ref. Standalone uses deterministic review/<review-scope-slug>-<snapshot12> or another approved ref. The return envelope carries report path, report SHA-256, report commit, and verified ref outside the immutable report.

The verified retained delivery report is the authoritative completed review ordinal. A delivery lineage permits three completed reviews and three corresponding fixes; a writer rejects any delivery ordinal above 3. Fix 3 proceeds to focused validation; passing validation creates the final clean delivery handoff without review 4.

The immutable report is snapshot evidence, not mutable workflow state. Review cold-resume state uses the caller-provided delivery handoff or the deterministic standalone runtime handoff. The retention envelope and runtime handoff remain outside the report bytes.

See Review for target adapters, routing, and execution flow.