Feature: Actor CLI exception handling contracts
  As a developer maintaining the actor CLI module
  I want the exception handling in _load_config_text and _compute_actor_impact to be correct
  So that malformed YAML produces user-friendly errors and actor removal stays resilient

  Background:
    Given an actor CLI runner

  # --- _load_config_text: yaml.YAMLError is caught and converted to BadParameter ---

  Scenario: Malformed YAML config produces a user-friendly error
    Given I have a malformed YAML actor config file
    When I run actor add with that config
    Then the actor command should fail with bad parameter

  # --- _compute_actor_impact: CleverAgentsError is caught defensively ---

  Scenario: _compute_actor_impact returns zero counts when session service raises CleverAgentsError
    When I call _compute_actor_impact with a session service that raises CleverAgentsError
    Then the impact result should be zero counts

  # --- _compute_actor_impact: OperationalError is caught defensively ---

  Scenario: _compute_actor_impact returns zero counts when session service raises OperationalError
    When I call _compute_actor_impact with a session service that raises OperationalError
    Then the impact result should be zero counts

  # --- _compute_actor_impact: ValidationError is caught defensively ---

  Scenario: _compute_actor_impact returns zero counts when session service raises ValidationError
    When I call _compute_actor_impact with a session service that raises ValidationError
    Then the impact result should be zero counts