Skip to content

CI quality gates

CI exists to protect: - accuracy and consistency - maintainability - review quality - predictable publishing

Typical gates: - MkDocs build (--strict) - Prompt schema validation - Prose linting (Vale) - Link checking (optional) - Unit tests (for automation scripts)