Feature: Anthropic chat provider coverage
  As a maintainer ensuring provider adapters stay validated
  I want Behave scenarios for the Anthropic chat provider
  So that the constructor guardrails and keyword handling stay covered

  @unit @providers @anthropic
  Scenario: Anthropic provider rejects missing API key
    Given I have sample provider domain inputs
    When I attempt to create an Anthropic chat provider without an API key
    Then the Anthropic provider creation should fail with "Anthropic API key is required"

  @unit @providers @anthropic
  Scenario: Anthropic provider forwards keyword overrides to ChatAnthropic
    Given I have sample provider domain inputs
    When I create an Anthropic chat provider with API key "sk-anthropic-unit" and model "claude-3-5-sonnet-20241022" with custom overrides
    And I request plan generation from the Anthropic provider
    Then the Anthropic provider should construct ChatAnthropic with api key "sk-anthropic-unit" and model "claude-3-5-sonnet-20241022"
    And the Anthropic provider should apply the custom overrides to ChatAnthropic
    And the Anthropic provider metadata should report name "anthropic" and model "claude-3-5-sonnet-20241022"