HAL9000
3368cba38f
CI / lint (push) Successful in 1m15s
CI / helm (push) Successful in 51s
CI / push-validation (push) Successful in 1m3s
CI / build (push) Successful in 1m17s
CI / quality (push) Successful in 1m45s
CI / typecheck (push) Successful in 2m14s
CI / security (push) Successful in 2m13s
CI / integration_tests (push) Successful in 3m48s
CI / e2e_tests (push) Successful in 4m21s
CI / unit_tests (push) Successful in 5m14s
CI / docker (push) Successful in 2m28s
CI / coverage (push) Successful in 11m51s
CI / status-check (push) Successful in 3s
CI / benchmark-regression (push) Has been cancelled
CI / benchmark-publish (push) Has been cancelled
Executes the systematic ACP -> A2A module rename per ADR-047. - Renamed all legacy ACP references to A2A throughout cleveragents.a2a module - Standardized all 22 exported symbols to A2A naming conventions - Added BDD test suite validating export completeness, zero ACP remnants, and documentation accuracy Closes #10583 Parent Epic: #8569 (A2A Standard Adoption)
41 lines
1.7 KiB
Gherkin
41 lines
1.7 KiB
Gherkin
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
|