fix: wire optional AI SDK into plugin installation - #69
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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.
Purpose
The plugin imports ai_gateway_client but did not declare a way to install it. Add an explicit ai extra pinned to the existing standard-library SDK from AAB #158. Default runtime dependencies and AI enablement remain unchanged.
Scope
Five files: package metadata/lock, existing AI tests, existing CI, README. No plugin source, model/auth API, workflow permissions, business switch or runtime configuration changes. CI explicitly installs test,ai and tests the real SDK, mocking only HTTP/OIDC network boundaries.
Validation
No actual model, paid API, provider, deployment, publishing or feedback call. Production consumer adoption, source authorization and remote validation remain separate.