evidence-review

Evidence-based verification is a quality gate that enforces systematic collection of test outputs, build logs, and screenshots to prove feature readiness. It ensures all P0 verification evidence is present and validated before shipping.

Run the verification workflow against your target codebase to collect test outputs, build logs, and screenshots. This enforces a reproducible quality gate that validates P0 evidence and provides remediation guidance for any failures.

Yes, the workflow handles cross-cutting verification across feature PRs, implementations, and final reviews. It systematically collects and validates evidence to enforce a rigorous quality gate before shipping software features.

The best way is using a systematic evidence collection workflow that captures screenshots alongside test outputs and build logs. This provides an objective, reproducible verification process that proves UI readiness with clear pass/fail criteria.

Yes, the evidence verification workflow operates without external dependencies. It functions as a standalone quality gate that systematically collects and validates test outputs, build logs, and screenshots directly from your target codebase.

Your review fails because the evidence-based quality gate enforces that all P0 verification evidence, including test outputs, must be present and validated. The workflow provides remediation guidance to help you collect and attach the missing evidence.