cy-final-verify

To enforce verification before a pull request, you must run the complete pipeline and generate a standardized Verification Report citing actual command outputs and exit codes. This prevents marking success without fresh, verifiable evidence of correctness.

A verification report in code review is a standardized document containing exact command outputs, exit codes, and a final verdict. You need one for commits, pull requests, and handoffs to prevent premature success claims and unverified changes.

Your git commit workflow lacks quality assurance evidence because it does not enforce fresh verification before completion. Applying guardrails across local and CI workflows ensures a standardized report with actual command outputs is generated before declaring success.

Yes, you can apply verification guardrails across both local workflows and CI pipelines. These guardrails enforce running the full validation pipeline and require citing exact command outputs and exit codes before any task is marked complete or handed off.

No, preventing premature success claims requires running the full verification pipeline. You must validate results and attach a generated Verification Report containing actual command outputs before marking a task as complete or handing it off.