Epic: A2A Protocol Integration #8423

Open
opened 2026-04-13 18:47:55 +00:00 by HAL9000 · 2 comments
Owner

Metadata

  • Commit Message: epic: implement A2A facade session and plan lifecycle operations for CLI
  • Branch Name: epic/a2a-protocol-integration

Background and Context

The v3.5.0 milestone (M6: Autonomy Hardening) requires the system to operate autonomously via the A2A (Agent-to-Agent) protocol. Following ADR-047 (A2A Standard Adoption), the ACP protocol has been superseded by A2A, and the facade layer must expose session management and plan lifecycle operations through the CLI. Additionally, an event queue with publish/subscribe semantics is required to coordinate asynchronous plan execution events across the system.

This Epic covers all work needed to make the A2A facade functional at the CLI level for v3.5.0, including session creation/teardown, plan lifecycle operations (start, pause, resume, cancel), and the event queue infrastructure that underpins autonomous execution.

Expected Behavior

  • The CLI exposes A2A facade commands for session management (agents session start, agents session end, etc.)
  • Plan lifecycle operations (start, pause, resume, cancel, status) are routed through the A2A facade
  • An event queue supports publish/subscribe for plan execution events (plan started, subplan spawned, decision recorded, plan completed, plan failed)
  • Events are durable enough to survive short process interruptions
  • The A2A facade correctly maps CLI invocations to the underlying plan lifecycle service

Acceptance Criteria

  • agents session start creates a new A2A facade session and returns a session ID
  • agents session end <session-id> terminates the session cleanly
  • agents plan start routes through the A2A facade and returns a plan ID
  • agents plan status <plan-id> reflects live plan state via the facade
  • agents plan cancel <plan-id> cancels an in-progress plan via the facade
  • Event queue publish(event) and subscribe(event_type, handler) are operational
  • Plan lifecycle events (started, subplan_spawned, decision_recorded, completed, failed) are published to the queue
  • Subscribers receive events in order with no dropped messages under normal load
  • All A2A facade operations are covered by BDD tests
  • nox passes with coverage >= 97%

Child Issues

Known related issues in v3.5.0 milestone (to be linked as children):

  • Issues related to A2A facade session management
  • Issues related to event queue publish/subscribe
  • Issues related to plan lifecycle CLI routing
  • Issue #8302: fix: custom automation profiles silently fall back to manual (automation profile resolution)
  • #8855 - Error Handling: Silent Suppression of RuntimeError in EventBusBridge
  • #8858 - Concurrency: A2aEventQueue is not thread-safe
  • #8856 - High: Incomplete A2A Operations in facade.py

Parent Legendary

Parent Legendary: #8450

Definition of Done

This Epic should be closed when:

  1. All acceptance criteria above are verified and passing
  2. The A2A facade session and plan lifecycle operations are functional end-to-end via CLI
  3. The event queue publish/subscribe is operational and tested
  4. All child issues are closed or explicitly deferred to a later milestone
  5. nox passes with coverage >= 97% including all A2A-related test suites
  6. A peer review has confirmed the A2A integration is correct and complete

Automated by CleverAgents Bot
Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor

## Metadata - **Commit Message:** `epic: implement A2A facade session and plan lifecycle operations for CLI` - **Branch Name:** `epic/a2a-protocol-integration` ## Background and Context The v3.5.0 milestone (M6: Autonomy Hardening) requires the system to operate autonomously via the A2A (Agent-to-Agent) protocol. Following ADR-047 (A2A Standard Adoption), the ACP protocol has been superseded by A2A, and the facade layer must expose session management and plan lifecycle operations through the CLI. Additionally, an event queue with publish/subscribe semantics is required to coordinate asynchronous plan execution events across the system. This Epic covers all work needed to make the A2A facade functional at the CLI level for v3.5.0, including session creation/teardown, plan lifecycle operations (start, pause, resume, cancel), and the event queue infrastructure that underpins autonomous execution. ## Expected Behavior - The CLI exposes A2A facade commands for session management (`agents session start`, `agents session end`, etc.) - Plan lifecycle operations (start, pause, resume, cancel, status) are routed through the A2A facade - An event queue supports publish/subscribe for plan execution events (plan started, subplan spawned, decision recorded, plan completed, plan failed) - Events are durable enough to survive short process interruptions - The A2A facade correctly maps CLI invocations to the underlying plan lifecycle service ## Acceptance Criteria - [ ] `agents session start` creates a new A2A facade session and returns a session ID - [ ] `agents session end <session-id>` terminates the session cleanly - [ ] `agents plan start` routes through the A2A facade and returns a plan ID - [ ] `agents plan status <plan-id>` reflects live plan state via the facade - [ ] `agents plan cancel <plan-id>` cancels an in-progress plan via the facade - [ ] Event queue `publish(event)` and `subscribe(event_type, handler)` are operational - [ ] Plan lifecycle events (started, subplan_spawned, decision_recorded, completed, failed) are published to the queue - [ ] Subscribers receive events in order with no dropped messages under normal load - [ ] All A2A facade operations are covered by BDD tests - [ ] `nox` passes with coverage >= 97% ## Child Issues _Known related issues in v3.5.0 milestone (to be linked as children):_ - Issues related to A2A facade session management - Issues related to event queue publish/subscribe - Issues related to plan lifecycle CLI routing - Issue #8302: fix: custom automation profiles silently fall back to manual (automation profile resolution) - #8855 - Error Handling: Silent Suppression of RuntimeError in EventBusBridge - #8858 - Concurrency: A2aEventQueue is not thread-safe - #8856 - High: Incomplete A2A Operations in facade.py ## Parent Legendary **Parent Legendary**: #8450 ## Definition of Done This Epic should be closed when: 1. All acceptance criteria above are verified and passing 2. The A2A facade session and plan lifecycle operations are functional end-to-end via CLI 3. The event queue publish/subscribe is operational and tested 4. All child issues are closed or explicitly deferred to a later milestone 5. `nox` passes with coverage >= 97% including all A2A-related test suites 6. A peer review has confirmed the A2A integration is correct and complete --- **Automated by CleverAgents Bot** Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.5.0 milestone 2026-04-13 18:49:56 +00:00
Author
Owner

Verified — A2A Protocol Integration is a Must Have for v3.5.0. The A2A facade session management and plan lifecycle CLI operations are explicit acceptance criteria per ADR-047. [AUTO-OWNR-1]


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

✅ **Verified** — A2A Protocol Integration is a Must Have for v3.5.0. The A2A facade session management and plan lifecycle CLI operations are explicit acceptance criteria per ADR-047. [AUTO-OWNR-1] --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
Author
Owner

🤖 Child Issues Created for Epic #8423

The following 5 child implementation issues have been created for this Epic as part of the v3.5.0 Autonomy Hardening milestone. Each child issue blocks this Epic and is assigned to milestone v3.5.0 (ID: 108).

# Issue Branch Prefix
1 #8542feat(a2a): implement A2A facade session lifecycle operations via CLI feat/v3.5.0-a2a-facade-session-lifecycle
2 #8543feat(a2a): implement A2A facade plan lifecycle operations via CLI feat/v3.5.0-a2a-facade-plan-lifecycle
3 #8545feat(a2a): implement A2A event queue publish/subscribe system feat/v3.5.0-a2a-event-queue
4 #8546feat(a2a): implement A2A hierarchical plan decomposition with 4+ levels of subplans feat/v3.5.0-a2a-hierarchical-decomposition
5 #8547feat(a2a): implement parallel subplan execution scaling to 10+ concurrent subplans feat/v3.5.0-a2a-parallel-subplan-execution

Labels Applied to All Child Issues

  • Type/Feature
  • Priority/High
  • MoSCoW/Must have
  • State/Verified

Coverage Requirement

All child issues require unit test coverage >= 97% and integration tests verifying all operations.


Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## 🤖 Child Issues Created for Epic #8423 The following 5 child implementation issues have been created for this Epic as part of the v3.5.0 Autonomy Hardening milestone. Each child issue **blocks** this Epic and is assigned to milestone **v3.5.0** (ID: 108). | # | Issue | Branch Prefix | |---|-------|---------------| | 1 | #8542 — `feat(a2a): implement A2A facade session lifecycle operations via CLI` | `feat/v3.5.0-a2a-facade-session-lifecycle` | | 2 | #8543 — `feat(a2a): implement A2A facade plan lifecycle operations via CLI` | `feat/v3.5.0-a2a-facade-plan-lifecycle` | | 3 | #8545 — `feat(a2a): implement A2A event queue publish/subscribe system` | `feat/v3.5.0-a2a-event-queue` | | 4 | #8546 — `feat(a2a): implement A2A hierarchical plan decomposition with 4+ levels of subplans` | `feat/v3.5.0-a2a-hierarchical-decomposition` | | 5 | #8547 — `feat(a2a): implement parallel subplan execution scaling to 10+ concurrent subplans` | `feat/v3.5.0-a2a-parallel-subplan-execution` | ### Labels Applied to All Child Issues - `Type/Feature` - `Priority/High` - `MoSCoW/Must have` - `State/Verified` ### Coverage Requirement All child issues require unit test coverage >= 97% and integration tests verifying all operations. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
Reference
cleveragents/cleveragents-core#8423
No description provided.