Preserve installed operator authority through MCP gateway - #756
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.
An installed Manager could read subordinate tasks but its canonical MCP comments were rejected: the gateway replaced the pre-bound local-operator provenance with ordinary-turn provenance. Preserve the explicit operator provenance only when an actor is already bound; ordinary authenticated callers and payload claims retain their existing restrictions.
Validation: 110 focused tests pass, including the real gateway and task mutation boundary for both the authorised operator and a payload-forged operator claim. This completes the remaining supervisory-write part of the capability repair; fresh installed Manager acceptance and deployment are in progress.