final-review

A final review assessment verifies implemented behavior matches the approved idea, spec, and plan before workflow closure by checking fidelity, regression risks, and unresolved gaps. It produces a ready-for-close-out recommendation with auditable findings.

A fidelity check confirms implemented behavior aligns with the approved idea, spec, and plan. It is needed during end-of-workflow verification after implementation review to catch drift, gaps, and ensure docs close-out readiness before approving closure.

Browser verification evidence for changed rendered local UI behavior is incorporated into the final review output by keeping validation results in view. The assessment writes findings to a non-overwriting round file in the workflow docs tree.

The latest implementation-review round and implementation summary are required inputs. The final review uses them to validate drift, check unresolved gaps, and generate the next final review round artifact for the workflow dossier.

No, final review writes a new non-overwriting round file to the workflow docs path at reviews/final/round-XX.md. This ensures the validation record remains auditable without relying on chat history, preserving all prior review artifacts.

If drift or gaps are found, the final review produces a loopback recommendation instead of ready-for-close-out. The assessment explicitly records a validated reviewer roster and concise findings-first results to guide resolution before closure can proceed.