docs: Clarify structured output artifacts#11
Open
cameroncooke wants to merge 1 commit intomainfrom
Open
Conversation
Document that streamed fragments are transient and final responses are driven from structured results. Clarify xcode-ide bridge payload handling and the structured-output union consumers should parse. Refs GH-360 Co-Authored-By: Codex <noreply@openai.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Clarify how XcodeBuildMCP structured output relates to transient streaming fragments and xcode-ide bridge artifacts.
The runtime now treats streaming fragments as live-only progress output, while final text and structured responses are rendered from final result contracts. These docs explain that boundary so consumers do not depend on streamed fragments for final state.
This also documents that xcode-ide bridge payloads can be represented as artifacts, and that consumers parsing structured output should handle the documented union of normal domain results and framework-level error results.
Refs GH-360