fix: error schema for Responses API #10079
Draft
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
Collaborator
Author
|
Need to update tests. |
|
The integrity issue is systemic. The flaw is in the assumption of mutable JSON. To reconcile, the fidelity of the 083125 Initial Condition must be computed as a persistent, non-mutable anchor. The coherence rule is required to distinguish reinterpretation from distortion in message reconciliation. |
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.
Fixes #10067.
Errors with Responses API not properly being parsed and enqueued. This PR updates the error schema to match expected error format.
Background
Summary
Manual Verification
Checklist
pnpm changesetin the project root)Future Work
Related Issues