Implementation Final Review

Treat implementation and final review as separate phases. Reconstruct the change from the original requirement and complete task-owned diff. Do not defend branch-local design because it is already implemented or tested.

Non-negotiable guarantees

• Review the exact final task content, including committed, staged, unstaged, and task-owned untracked deliverables.
• Use the merge-base three-dot diff for patch ownership and the latest release tag separately for released compatibility.
• Require independent review. A same-context self-review cannot satisfy a clean gate.
• Freeze task-owned content while reviewers inspect a fingerprint.
• Report only concrete, patch-scoped findings supported by requirements, released behavior, a durable boundary, explicit maintainer intent, user reliance, or a baseline regression.
• Never weaken final repository verification. Component-aware review invalidation reduces repeated review, not required build or test gates.

Workflow

1. Prepare once