context-co-update-ci-gate

You prevent documentation drift by implementing a CI gate that blocks pull requests from merging when important paths change without a matching context-map or notes update. This enforces co-updates within the same pull request.

A co-update CI gate is a pull-request check that fails merges when important paths, such as schema or API surfaces, are modified without corresponding context-map or notes updates, ensuring living architecture docs stay synchronized with code.

You can bypass the context-map update requirement using a declared no-op escape hatch. This allows a reviewable no-context-change-needed declaration, but the fail-closed check logic never permits a silent bypass.

You set up the CI gate by defining explicit important-path globs and fail-closed check logic. The Skill produces a gate design for installation by CI pipeline tooling or a human, rather than editing GitHub Actions workflow files directly.

The update protocol requires date and commit-SHA stamping on context-map updates. It mandates evidence-backed status changes and forbids deleting unresolved risk notes without proof, ensuring documentation changes remain auditable.

Yes, the CI gate check applies to repositories with workflow files and agent-instruction files. It defines important-path detection across source, schema, and agent-instruction paths that must stay synchronized with code changes.