Harness Doc Drift

Review only concrete documentation mismatches introduced by the pull request. "No drift" is a normal result.

Workflow

Resolve the pull request, repository, and base ref. Review the diff in base-branch context; do not audit unrelated existing content.
Read the repository's AGENTS.md, then its linked contributor and harness documentation. Treat the closest document for the changed workflow as authoritative.
Inspect changed harness-sensitive surfaces first:
- build manifests and task files;
- scripts, hooks, CI workflows, command surfaces, and self-tests;
- routing documentation adjacent to changed behavior.
Compare the changed behavior with its closest source-of-truth documentation. Check command existence and contracts, script inventories, mutability labels, routing links, and planned-versus-current wording.
Check operator-doc bloat only if the PR edits an agent-loaded or happy-path operator document. Flag a newly primary preview, scaffold, or non-default path; or newly duplicated caveat/command text. Keep this advisory.
Report only findings with a changed file, affected document, and precise suggested edit. Separate must-fix drift from advisory bloat. If no meaningful drift exists, post a brief no-drift comment or omit it when the PR does not touch harness surfaces.