Human Review

Protect human attention. Let automated review handle mechanically checkable correctness; ask the human to accept or reject the consequential promises the change introduces.

Establish trustworthy coverage

Read the request, repository instructions, current diff or named change, and any relevant specs or project decisions. Inspect the actual product and rerun the smallest checks needed to support each claim. Treat prior summaries as claims, never as proof. Review the completed work without fixing or broadening it.

Before compressing, account for every changed product behavior, access or data boundary, external contract, and failure or recovery path. Give each one a disposition: summary, human question, mechanical issue, or unverified. Keep this coverage note behind the evidence path, but surface any release blocker or material unverified limit in the overview. This check exists because compression can otherwise make an omitted change invisible.