fix: per-call usage model and own-property choice check - #16
Merged
TheGreatAxios merged 1 commit intoSep 27, 2026
Conversation
Closes CL-9438
TheGreatAxios
added this pull request to stack #13
September 27, 2026 00:43
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.
Closes CL-9438
inference.usagesource model now comes from the response envelope'smodel, falling back to the configured endpoint model, so concurrent calls can't report each other's model.checkAnswersusesObject.hasOwnfor the choice check, so inherited keys likeconstructorare rejected as illegal options.Tests:
src/adapter.test.ts(usage model after two interleavedbuildRequestcalls) and a newinherited optioncase insrc/evaluate.test.ts; both failed before the fix.