Repository navigation
Qualify saved schema rejection - #628
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 structured qualification assumed a saved Agent could retain a schema rejected by its explicitly selected Harness. It now checks rejection at Agent update, including unchanged stored configuration, and separately checks inline Session rejection without creating a Session. Both raw HTTP and the pinned SDK must return the existing typed errors and field paths.
Validation: the original nine live structured-output checks passed unchanged on fc21069; the corrected two admission negatives passed separately without model calls or another restart. Independent review found no issues. Python syntax, unchanged-positive AST comparison, and diff hygiene passed.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.