Feature: Automation Profile CLI coverage boost
  As a developer
  I want to cover remaining branches in automation_profile CLI module
  So that coverage reaches the 97% threshold

  Background:
    Given an automation profile coverage CLI runner

  Scenario: Delete from in-memory repo when profile does not exist
    When I delete a non-existent profile from the in-memory repo
    Then a NotFoundError should be raised from the repo

  Scenario: Threshold summary returns compact string
    When I call threshold summary on a built-in profile
    Then the threshold summary should contain strategize execute and apply values

  Scenario: Guarded profile config passes docs schema and model
    When I validate a guarded profile config against docs schema and model
    Then the guarded profile config should pass schema and model validation

  Scenario: Add profile with non-dict YAML content aborts
    Given a YAML file containing a list instead of a dict
    When I run automation-profile add with that non-dict YAML file
    Then the automation-profile coverage command should abort
    And the automation-profile coverage output should contain "mapping"

  Scenario: Add profile triggers FileNotFoundError from open
    When I run automation-profile add with a config that triggers FileNotFoundError
    Then the automation-profile coverage command should abort

  Scenario: Add profile triggers ValidationError from service
    Given a YAML file that triggers a ValidationError from the service
    When I run automation-profile add with that validation-error YAML file
    Then the automation-profile coverage command should abort
    And the automation-profile coverage output should contain "Validation"

  Scenario: Add profile triggers CleverAgentsError from service
    Given a YAML file that triggers a CleverAgentsError from the service
    When I run automation-profile add with that cleveragents-error YAML file
    Then the automation-profile coverage command should abort
    And the automation-profile coverage output should contain "Error"

  Scenario: Remove profile without --yes prompts confirmation and user declines
    Given a custom coverage profile "acme/removable" has been added
    When I run automation-profile remove "acme/removable" without --yes and decline
    Then the automation-profile coverage output should contain "Cancelled"

  Scenario: Remove profile without --yes prompts confirmation and user confirms
    Given a custom coverage profile "acme/removable2" has been added
    When I run automation-profile remove "acme/removable2" without --yes and confirm
    Then the automation-profile coverage remove should succeed
    And the automation-profile coverage output should contain "removed"

  Scenario: Remove profile triggers ValidationError
    Given a custom coverage profile "acme/valerr" has been added
    When I run automation-profile remove "acme/valerr" with validation error
    Then the automation-profile coverage command should abort
    And the automation-profile coverage output should contain "Validation"

  Scenario: Remove profile triggers CleverAgentsError
    Given a custom coverage profile "acme/caerr" has been added
    When I run automation-profile remove "acme/caerr" with CleverAgentsError
    Then the automation-profile coverage command should abort
    And the automation-profile coverage output should contain "Error"

  Scenario: List profiles triggers CleverAgentsError
    When I run automation-profile list with a CleverAgentsError from service
    Then the automation-profile coverage command should abort

  Scenario: Show profile triggers CleverAgentsError
    When I run automation-profile show with a CleverAgentsError from service
    Then the automation-profile coverage command should abort

  Scenario: Emit automation level deprecation warning directly
    When I call emit_automation_level_deprecation_warning
    Then a DeprecationWarning should be emitted