review5-accept

Code diff validation compares actual code changes item-by-item against a finalized review document as the sole baseline. This ensures only agreed implementation items are accepted before closing the review loop.

Strict guardrails refuse to proceed with the acceptance gate if stage 4 is not completed in the document. The process enforces backlog checks and requires stage-4 completion before any detailed diff comparison.

Workflow rollback checks backlog existence for delayed items before detailed comparison. Accepted or returned results are written in a single batch update, allowing the review process to finish or roll back to execution.

Retrying acceptance carries forward prior return history instead of overwriting it. The batch-update appends new return reasons into existing Accept blocks, ensuring traceable retries throughout the review workflow.

Filtering review items for final acceptance involves selecting only those marked as agreed and implemented. The process re-reads the document via a Read tool and validates stage-4 completion before proceeding.