freemo
0c301ac581
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 44s
CI / lint (pull_request) Successful in 3m19s
CI / unit_tests (pull_request) Failing after 3m42s
CI / quality (pull_request) Successful in 3m48s
CI / typecheck (pull_request) Successful in 4m55s
CI / security (pull_request) Successful in 5m6s
CI / docker (pull_request) Has been skipped
CI / e2e_tests (pull_request) Successful in 5m9s
CI / integration_tests (pull_request) Successful in 6m52s
CI / coverage (pull_request) Failing after 19m27s
CI / benchmark-regression (pull_request) Successful in 48m13s
CI / status-check (pull_request) Failing after 1s
The A2A facade now exposes 42 operations (31 extension + 11 legacy) after the spec-aligned _cleveragents/ extension methods were added. Update the BDD assertion and docs to match the actual count.
46 lines
1.9 KiB
Gherkin
46 lines
1.9 KiB
Gherkin
@mock_only
|
|
Feature: A2A CLI facade integration
|
|
As a CleverAgents developer
|
|
I want CLI commands to route through the A2A local facade
|
|
So that all operations comply with the A2A protocol data flow
|
|
|
|
Scenario: CLI bootstrap creates a wired facade
|
|
Given a facade created via the CLI bootstrap
|
|
Then the facade should support all 42 operations
|
|
And the facade should be cached on subsequent calls
|
|
|
|
Scenario: Session create routes through facade
|
|
Given a facade with a mock session service
|
|
When I dispatch a session.create operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan create routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.create operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan execute routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.execute operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan apply routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.apply operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan status routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.status operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan diff routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.diff operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Facade notification is best-effort
|
|
Given a facade that raises an error on dispatch
|
|
When I call the plan notify_facade helper with operation "plan.create"
|
|
Then no exception should propagate to the caller
|