Require drift audit before maintenance no-op#161
Merged
Conversation
This was referenced Jul 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
no_changesCloses #160.
Source relationship and scope
The native
technical-docs-maintenance-agent.agent.jsonpackage is the repository's sole executable instruction authority for this lane; the retired manifest/flow/pipeline source family and generator are not present in the current architecture. This is an instruction-only package contract change plus deterministic validation and provenance fixtures. It does not change runtime code, tool policy, writable paths, publication behavior, bootstrap agents, user-doc agents, or the skills agent. The runtime impact is therefore no broader than the source evidence in #160: maintenance no-op classification now requires the bounded audit that the failing runs lacked.Verification capability is deterministic at three boundaries: required instruction phrases, historical package bytes/digest/provenance, and real Agents API import plus the pinned WP Codebox reusable-workflow contract.
Stranger-runnable tests
php tests/validate-docs-agent-packages.phpphp tests/validate-external-native-package-sources.phpphp tests/repair-docs-links-smoke.php78e2dd409010f98fa4d26cdd72572117384ab18d, then run:AGENTS_API_DIR=/path/to/agents-api php tests/native-agent-import.php65cc5fb4699cb7c2df13d04b4715c97097ac7565, then run:WP_CODEBOX_DIR=/path/to/wp-codebox php tests/validate-wp-codebox-run-agent-task-contract.phpactionlint .github/workflows/*.ymlgit diff --check 53f43bc6433d2631750edabcb458a77db55aa8cb..HEADAll tests passed locally.
Compatibility impact
No schema, runtime API, package slug, enabled tool, write gate, writable-path, or publication contract changes. Existing clean maintenance no-ops remain valid after audited claims match source. Only the technical maintenance package bytes and their required immutable digest/provenance declarations change.
AI assistance
Implemented and verified with AI assistance from
openai/gpt-5.6-sol.