Validate requested structured outputs against JSON Schema #100
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/llm-log!100
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/58-structured-output-anomaly"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tracks the third bounded detector family from #58, stacked on #92.
RED-first scope:
response_format.type=json_schemacontracts and Responses APItext.format.type=json_schemacontracts;delta.contentand Responsesresponse.output_text.deltatext before parsing/validation;structured_output_invalid_jsononly for complete outputs under a valid supplied schema contract;structured_output_schema_violationwith safe validator/path evidence for valid JSON that violates the supplied schema;finish_reason=length, Responsesincomplete/failed states, ordinary text mode, and invalid/unresolvable request schemas are non-blame states;This slice is observe-only model-behavior evidence. Repetition/looping, output-length baselines, encoding corruption, self-correction/canary drift and notification integration remain separate #58 slices.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.