Repository navigation
test: cover Copilot SDK reasoning discovery and translation - #68
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.
Summary
A working Local-chat picker does not prove Copilot SDK discovery. Add contract tests for the SDK's exact reasoningEffort schema key, its VS Code 1.141 effort filtering, and translation of selected values into native requests. Test discovery with and without Context Window controls.
Cover graded efforts and native toggle/budget models, plus endpoint-native request translation. Document that off/on/auto and separate budget controls remain Local-chat features.
This carries the SDK compatibility coverage from OpenAI PR #77. The runtime already publishes the expected key, so this PR adds tests and documentation without changing its effort schema or transport behavior.
Include a patch Changeset so the SDK compatibility documentation and coverage ship in the next extension release.
Verification
Checklist