Modernize hosted MCP boundaries for 2026-07-28 - #30
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.
Summary
Compatibility
The v2 delegation wire contract is aligned to merged Sagasmith-core commit 0ac316655687757203a9df1b2eb81669ec1d2d78. No component lock is changed here; the coordinated lock update should follow merged domain-server commits.
Validation
No production data, paid model or external service was used. Rollback can select protocolMode legacy while retaining the request-scoped identity boundary; the legacy bridge is compatibility-only and must not become the long-term authority model.