Feature: A2A Module Naming Regression Tests
  Verify zero ACP references remain after module rename
  and ensure A2A module imports work correctly

  Background:
    Given the A2A module is properly installed
    And no ACP references exist in the codebase

  Scenario: Import A2A facade from new module path
    When I import the A2A facade from "cleveragents.a2a"
    Then the import succeeds
    And the facade is an instance of A2aLocalFacade

  Scenario: Import A2A clients from new module path
    When I import A2A clients from "cleveragents.a2a"
    Then the import succeeds
    And the clients module contains ServerClient

  Scenario: Import A2A models from new module path
    When I import A2A models from "cleveragents.a2a"
    Then the import succeeds
    And the models module contains A2aRequest

  Scenario: Import A2A errors from new module path
    When I import A2A errors from "cleveragents.a2a"
    Then the import succeeds
    And the errors module contains A2aError

  Scenario: Import A2A events from new module path
    When I import A2A events from "cleveragents.a2a"
    Then the import succeeds
    And the events module contains A2aEventQueue

  Scenario: Old ACP import path raises ImportError
    When I attempt to import from old "cleveragents.acp" path
    Then an ImportError is raised
    And the error message indicates the module does not exist

  Scenario: A2A __init__ exports all public symbols
    When I import from "cleveragents.a2a"
    Then the module exports A2aLocalFacade
    And the module exports ServerClient
    And the module exports A2aRequest
    And the module exports A2aError
    And the module exports A2aEventQueue

  Scenario: No ACP references in source code
    When I scan the source code for ACP references
    Then no "acp" imports are found
    And no "from cleveragents.acp" statements are found
    And no "import cleveragents.acp" statements are found

  Scenario: A2A module structure is complete
    When I inspect the A2A module structure
    Then the module contains __init__.py
    And the module contains facade.py
    And the module contains clients.py
    And the module contains models.py
    And the module contains errors.py
    And the module contains events.py
    And the module contains asgi.py
    And the module contains transport.py
    And the module contains versioning.py
    And the module contains server_config.py
    And the module contains cli_bootstrap.py

  Scenario: A2A facade initialization works correctly
    When I initialize the A2A facade
    Then the facade initializes without errors
    And the facade has required methods
    And the facade can be used for A2A operations