ci-merge-gate

To enforce CI merge-gate checks on pull requests, automate contract tests, governance checks, and requirement traceability validation against FR/NFR specifications before merging. This ensures end-to-end validation by verifying modified spec files and workflow definitions.

Requirement traceability validation in a CI workflow verifies that modified spec files align with RTM, FR, and NFR documentation. It ensures governance checks and contract tests pass before merge, maintaining end-to-end compliance across pull requests.

Yes, you can run pull request merge-gate validations locally before pushing by triggering the included scripts from the repository root. This provides local validation parity with CI checks for spec, governance, and traceability verification.

Yes, the CI merge-gate check applies to modified spec files, workflow definitions under .github/workflows/allium-specs.yml, and scripts under scripts/. It ensures end-to-end validation and traceability alignment with FR/NFR requirements.

A CI merge-gate for requirement compliance includes contract tests, governance checks, version checks, and requirement traceability validation. These checks enforce FR-0.2 and NFR-O1 expectations during pull requests to ensure consistent verification before merge.

You need to run CI merge-gate validations for spec files whenever modifications are made during a pull request. This ensures governance alignment, traceability with RTM/FR/NFR docs, and contract compliance are verified before merging.