Repository navigation
[codex] Coordinate governance rollout - #112
Merged
Merged
Conversation
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
1 participant
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.
Why
The server governance rollout must not change installed cron while a proposal is pending or rejected.
Changes and validation
Add an HTTP polling regression that installs the effective manifest, verifies an unchanged response leaves it intact, then applies an approved removal and persists the new version with mode-0600 credential state. The test uses an isolated fake crontab executable and never touches host cron. Document governance as server-side with an unchanged HTTPS v2 protocol.
Go tests pass. This change contains tests and documentation only; no runtime behavior or agent release is required for rollout.