harness-contract-change

To synchronize agent documentation and manifests, you patch the repository to reflect a harness-contract change and run the agent validation and CI gate to ensure alignment across docs, manifests, and validators.

Coordinating AGENTS.md changes involves harmonizing agent contract documentation and tooling across docs, manifests, and CI surfaces, ensuring the canonical state is reflected across all surfaces in a single patch.

You need to update repo manifests and CI workflow classifications together when modifying the repository's agent contract, ensuring changes to AGENTS.md, docs index, validation scripts, and contributor wrappers are aligned.

Yes, you can update contributor-facing guides like CONTRIBUTING.md and PR templates as part of modifying the repository's agent contract, synchronizing these wrappers alongside docs, manifests, and validation scripts.

Agent validation fails after separate edits because the canonical state is not reflected across all surfaces, causing misalignment that make agent-validate and agent-ci-gate checks detect durable divergences recorded as indexed debt entries.

The best way to manage divergences when changing agent documentation and tooling is to enforce alignment through make agent-validate and agent-ci-gate checks, recording any durable divergences as indexed debt entries.