aibdd-refactor-evaluate

To verify a code refactor passes development constitution compliance, you strictly check the completed refactor evidence for any MUST or MUST NOT violations within the specified product-code scope, treating violations as veto-level failures to ensure safety.

Validating acceptance test suite results for a completed refactor requires confirming the only acceptable evidence is the final full acceptance suite report, and failing the evaluation if there are any test failures, errors, or improper skip, xfail, deselect, or collection omissions.

A quality gate for refactoring is an evaluation step that prevents completed refactoring work from silently breaking development rules or slipping in invalid acceptance test results, needed when finalizing any AIBDD refactor workflow.

You cannot use a partial acceptance test report to pass a refactor quality gate. The evaluation explicitly fails if it detects any improper skip, xfail, deselect, or collection omissions, requiring the final full-suite acceptance report as the only valid evidence.

Generating a machine-readable refactor evaluation report requires a refactor handoff payload containing explicit artifact pointers, including the resolved paths for the final full acceptance suite report and the development constitution file.