fix(teams): preserve Gemini model provider provenance - #1332
Draft
FerroxLabs wants to merge 1 commit into
Draft
FerroxLabs wants to merge 1 commit into
FerroxLabs wants to merge 1 commit into
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.
A rejected Gemini Team default could be rebound to Google OAuth with the rejected model ID. For example, disabled
moonshot/kimi-k2.7-coderesolved asgoogle-auth-gemini + kimi-k2.7-codewhenever OAuth credentials existed.This change retains supported explicit Google OAuth selections, keeps valid enabled API selections on their owning provider, and routes rejected object/string defaults to the existing shared Gemini
automode without carrying the rejected provider key or base URL. A three-member fixture covers conversation persistence and worker construction.Validation:
Live Google OAuth provider acceptance was unavailable on the verification machine and remains unverified. No release or issue closure is included.
Refs #983