Repository navigation
docs: select released MCP error fidelity and link Constellation reference - #2099
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
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.
The explicit MCP profile still pins the adapter that reports server-declared tool failures as success. Update that recipe to the immutable source of published MCP 0.3.1 and link the runnable Constellation reference.
Keep the earlier Unified 0.94.1/MCP 0.3.0 retrieval evidence separate, and state the reference’s explicit-profile, prepared-worker and deterministic-provider limits. Defaults, runtime code and saved conversations are unchanged.
Validation: checked the published tag/source tree, qualified package receipt, public reference link and documentation diff. No application test rerun for this documentation-only change.