cm-quality-gate

Pre-deploy quality gates block deployments by running the test:gate suite and verifying all checks pass with fresh output. You can enforce them in CI/CD pipelines by executing npm run test:gate before any deployment step.

Evidence-based verification requires fresh test output proving all gates passed before allowing any completion claim or deployment. It prevents releasing software without verified, up-to-date test results from the test:gate suite.

Frontend safety checks run as part of the test:gate suite to catch template or code issues before production release. Execute npm run test:gate to automatically apply these checks within your pre-deploy quality gates.

Automated test gates apply to CI/CD workflows across both frontend and backend apps. They enforce test suites and frontend safety checks, ensuring no deployment proceeds until all gates pass with fresh verification output.

Deployment should be blocked without passing test gates to enforce evidence-based verification and prevent unverified code from reaching production. Quality gates ensure no completion claim proceeds without fresh test output proving all checks passed.

The best way to prevent unverified deployments is implementing pre-deploy quality gates that run the test:gate suite and block releases until fresh verification output confirms all tests and frontend safety checks pass.