fix(governance): preserve capability boundaries and valid policy overrides - #135
Merged
Conversation
…rides Signed-off-by: rldyourmnd <danil@nddev.it.com>
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.
A private repository on a plan without rulesets could not use any GDS governance operation: the optional ruleset read failed the entire snapshot. Separately, changing a managed field to observed/ignored retained its inherited desired value and produced an invalid compiled contract.
Retain available observations and mark the exact ruleset product restriction explicitly. Authorization errors and rate limits still fail closed, unavailable managed fields refuse planning, and availability participates in the optimistic-concurrency digest without changing old fully observed digests. Remove inherited values and their provenance when a higher policy tier selects observed/ignored.
Validation: both defects reproduced with regression tests before the fix; all Go quick validation passes, relevant compiler/provider/governance race tests pass, app governance tests pass, and all 47 Python tests pass from the hashed test lock. Tests also prove available settings can be applied and read back while unavailable rulesets remain explicit, and historical digest compatibility is preserved.