fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER

Adds ProviderType.GEMINI to the provider registry fallback order, right after ProviderType.GOOGLE. This ensures Gemini-only users can use auto-discovery via get_default_provider_type() when only GEMINI_API_KEY is set. Also removes the @tdd_expected_fail tag from the TDD scenario in features/ tdd_gemini_fallback_order_4750.feature since the test now passes.
2026-05-11 00:56:34 +00:00
2 changed files with 2 additions and 1 deletions
@@ -3,7 +3,7 @@ Feature: TDD: ProviderType.GEMINI missing from ProviderRegistry.FALLBACK_ORDER
  I want get_default_provider_type() to return ProviderType.GEMINI via the fallback chain
  So that Gemini-only users can use auto-discovery without setting GOOGLE_API_KEY

-  @tdd_issue @tdd_issue_4750 @tdd_expected_fail
+  @tdd_issue @tdd_issue_4750
  Scenario: Gemini-only user gets GEMINI as default provider via fallback order
    Given a ProviderRegistry configured with only gemini_api_key set
    And CLEVERAGENTS_DEFAULT_PROVIDER is not set for tdd test
@@ -220,6 +220,7 @@ class ProviderRegistry:
        ProviderType.OPENAI,
        ProviderType.ANTHROPIC,
        ProviderType.GOOGLE,
+        ProviderType.GEMINI,
        ProviderType.AZURE,
        ProviderType.OPENROUTER,
        ProviderType.GROQ,