Feature: Fallback order includes ProviderType.GEMINI
  As a developer
  I want ProviderType.GEMINI to be included in ProviderRegistry.FALLBACK_ORDER
  So that Gemini becomes a valid fallback when no higher-priority provider is configured

  @unit @providers @registry @fallback
  Scenario: GEMINI appears in FALLBACK_ORDER list
    Given I have the ProviderRegistry class
    When I check the FALLBACK_ORDER contents
    Then GEMINI should be present in the fallback order
    And OPENAI should still be first in the order
    And ANTHROPIC should still be second in the order

  @unit @providers @registry @fallback
  Scenario: Gemini-only provider gets selected as default via fallback order
    Given a registry with only gemini API key set to "sk-gemini-test"
    And CLEVERAGENTS_DEFAULT_PROVIDER is not set
    When I request the default provider type
    Then the gemini fallback default should be ProviderType "GEMINI"

  @unit @providers @registry @fallback
  Scenario: Gemini fallback selected after OPENAI, ANTHROPIC, GOOGLE are unconfigured
    Given a registry with only gemini API key set to "sk-gemini-test"
    And CLEVERAGENTS_DEFAULT_PROVIDER is not set
    When I iterate through FALLBACK_ORDER and find the first configured provider
    Then GEMINI should be the first configured provider found

  @unit @providers @registry @fallback
  Scenario: Gemini in fallback order does not affect explicit env override
    Given a registry with only gemini API key set to "sk-gemini-test"
    And CLEVERAGENTS_DEFAULT_PROVIDER is set to "gemini"
    When I request the default provider type
    Then the gemini fallback default should be ProviderType "GEMINI"

  @unit @providers @registry @fallback
  Scenario: Gemini with all other providers unconfigured returns None only when GEMINI also has no key
    Given a gemini-registry with no API keys configured
    And CLEVERAGENTS_ALLOW_MOCK_PROVIDER is not set
    When I request the default provider type from a clean registry
    Then the clean gemini registry default should be None