Feature: A2A Module Rename and Symbol Standardization
  As a developer
  I want all A2A symbols to be standardized
  So that the codebase uses consistent A2A naming conventions

  Scenario: A2A module exports all required symbols
    When I import from cleveragents.a2a
    Then I should have access to A2aError
    And I should have access to A2aErrorDetail
    And I should have access to A2aEvent
    And I should have access to A2aEventQueue
    And I should have access to A2aHttpTransport
    And I should have access to A2aLocalFacade
    And I should have access to A2aNotAvailableError
    And I should have access to A2aOperationNotFoundError
    And I should have access to A2aRequest
    And I should have access to A2aResponse
    And I should have access to A2aStdioTransport
    And I should have access to A2aVersion
    And I should have access to A2aVersionMismatchError
    And I should have access to A2aVersionNegotiator
    And I should have access to AuthClient
    And I should have access to RemoteExecutionClient
    And I should have access to ServerClient
    And I should have access to ServerConnectionConfig
    And I should have access to StubAuthClient
    And I should have access to StubRemoteExecutionClient
    And I should have access to StubServerClient
    And I should have access to TransportSelector

  Scenario: A2A module has no ACP references
    When I check the A2A module for ACP references
    Then there should be no ACP imports
    And there should be no ACP class names
    And there should be no ACP function names

  Scenario: A2A module is properly documented
    When I check the A2A module documentation
    Then the module docstring should mention A2A
    And the module docstring should not mention ACP