Repository navigation
ops: candidate promotion evidence and pre-stop drain safety - #58
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
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.
Delivered
Operator fixes
Shared read-only guard refuses active API/worker work and credentials before stopping staging; authority helper now reads snapshot.view.status and allows retained terminal history. Tests assert no stop/pin/backup side effects on refusal. Exclusive maintenance remains required; this is not an atomic ingress lock. No routing/VPN/front-end source edits or disk resize.
Verification
58 Linux Python tests with one local age-tool skip; CI installs age. Documentation links/diff checks pass. Release candidate runtime is unchanged; this PR updates operator tooling and records completed promotion.