orthoplus-quality-gate

To run a quality gate across a monorepo, execute a coordinated validation script that ensures backend build, lint, and tests, plus frontend type-check and build pass before merging. This enforces merge safety by blocking P0 failures from deployment.

An architecture guard enforces CI validation by applying deterministic rules, such as arch-guard.sh, to block changes that violate architecture constraints. It ensures structural compliance before merging changes into the monorepo.

You block broken frontend builds by enforcing a quality gate that requires frontend type-check, lint, and build steps to pass. P0 failures block deploys entirely, while warnings require documented justification to proceed.

Yes, you can validate both backend and frontend architecture by running a full quality gate script in a single pass. This coordinates deterministic CI-style checks across the monorepo to enforce merge safety policies.

When a quality gate detects a P0 failure during CI validation, it blocks the deploy entirely. Merge safety policies require the deterministic checks to pass, ensuring broken or non-compliant changes do not reach production.

Yes, warnings flagged by the quality gate must be handled via documented justification before merging. While P0 failures block deploys completely, warnings are permitted with explicit reasoning to maintain monorepo compliance.