Fix Labkit remote governance capability boundary - #253
Merged
Conversation
Disclosure-Reviewed: reviewed — public-safe only, private facet kept out of this commit
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.
What changed
labkit doctor --remotescoped to publicly observable projection/workflow parity--remote-governancefor auto-merge and required-check auditing with an Administration-read credentialRoot cause
The projection supervisor used the source repository's
github.tokento query cross-repository administration state. GitHub omitted or rejected that state, and Labkit collapsed the unavailable result intofalse, producing issue #235 even though Interlock's controls were enabled.Validation
uv run --project labkit --extra dev pytest -q labkit/tests(82 passed)--remote--remote-governanceAddresses #235.