wa:deploy-review

Dev-to-main deployment readiness gating verifies merge status, validation verdicts, release tags, changelog updates, and tracker issue completion to produce a clear PASS or FAIL verdict. This prevents faulty or incomplete feature branches from being promoted to main.

A deploy readiness gate enforces a pre-promotion checklist for dev-to-main merges by evaluating stage-based criteria like merge completion and changelog verification. It applies rigor-based rules to determine if failures block the workflow or allow overrides.

Generating an auditable deployment review report involves scanning the current feature context and writing a DEPLOY-REVIEW.md artifact. This document summarizes the deployment checklist, the final gate verdict, and any blocking remediation steps required.

Yes, deployment readiness checks can be optionally scoped by a feature slug. This targets the validation of merge-to-dev status, release tagging, and tracker issue closure specifically for an individual feature's lifecycle workflow.

Lite, Standard, and Strict rigor levels determine which checklist failures block the dev-to-main workflow and whether overrides are allowed. Higher rigor levels enforce stricter release readiness requirements across merge status, validations, and changelog updates.

Dev-to-main promotion fails the deployment gate when release readiness criteria beyond a successful merge are unmet. The gate requires validation verdicts, release tag presence, changelog updates, and tracker issue closure to all pass before allowing promotion.