feat(tangle): transport runtime MCP attachments - #316
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.
Runtime refuses direct Sandbox managers before inference because the Tangle provider does not advertise or transport runtime MCP attachments. Carry the canonical attachment contract through Sandbox create and turn requests while preserving the authored profile and its digest.
The provider checks the selected backend catalog before provisioning. It rejects unavailable support, disabled attachments, profile alias collisions, and custom mappers that drop or replace attachments. Sandbox SDK 0.39.0 is required because it preserves these bindings when a turn overrides only model credentials.
Validation: all 280 Tangle provider tests pass locally, including nine attachment regressions and a real SDK HTTP create/turn test. The original eight regressions fail on the unmodified base. Provider typecheck and build pass. Server revision d5b49d576 contains Sandbox #7191, and the live authenticated OpenCode catalog reports runtimeAttachments.mcp=true. Actual remote tool execution is being checked independently through Discovery Lab; catalog support alone is not that proof.