verification-before-completion

To prevent false completion reports, enforce verification before completion by requiring observed evidence like concrete test outputs, rather than relying on reasoning or expectations alone.

A verification gate for build outputs is a hard requirement that mandates concrete command and test results to prove a fix works before claiming the task is complete.

To report unverified limitations, state exactly what remains unverified and specify the concrete build or test outputs needed to confirm the resolution, instead of fabricating results.

Your debugging fix fails the quality gate because completion claims using should or probably rationalizations are blocked unless explicitly backed by observed test outputs and specific re-checks.

You cannot close a readiness statement without concrete command outputs, because the verification gate requires explicit observed evidence and specific re-check confirmation of the originally reported problem.