feat(a2a): implement A2A facade plan lifecycle operations via CLI #8543

Open
opened 2026-04-13 20:37:47 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit message type: feat
  • Scope: a2a
  • Branch name prefix: feat/v3.5.0-a2a-facade-plan-lifecycle

Background and Context

As part of Epic #8423 (A2A Protocol Integration), the A2A facade must expose plan lifecycle operations (create, start, status, cancel) via the CLI. This enables the autonomy hardening flow to manage plan execution through the A2A protocol.

This issue blocks Epic #8423.

Expected Behavior

  • agents a2a plan create <session-id> <spec> creates a new plan within a session
  • agents a2a plan start <plan-id> starts plan execution
  • agents a2a plan status <plan-id> shows current plan status
  • agents a2a plan cancel <plan-id> cancels a running plan

Acceptance Criteria

  • agents a2a plan create command is registered and functional
  • agents a2a plan start command is registered and functional
  • agents a2a plan status command is registered and functional
  • agents a2a plan cancel command is registered and functional
  • Plan state is persisted to the database
  • Integration tests verify all plan lifecycle operations
  • Unit tests achieve >= 97% coverage

Subtasks

  • Register a2a plan subcommands in the CLI
  • Implement A2A plan create service function
  • Implement A2A plan start service function
  • Implement A2A plan status service function
  • Implement A2A plan cancel service function
  • Write integration tests for all plan lifecycle operations
  • Write unit tests for service functions

Definition of Done

  1. All A2A plan lifecycle CLI commands are functional
  2. Integration tests verify all operations
  3. Unit tests pass with >= 97% coverage
  4. Code reviewed and merged to main branch

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

## Metadata - **Commit message type**: `feat` - **Scope**: `a2a` - **Branch name prefix**: `feat/v3.5.0-a2a-facade-plan-lifecycle` ## Background and Context As part of Epic #8423 (A2A Protocol Integration), the A2A facade must expose plan lifecycle operations (create, start, status, cancel) via the CLI. This enables the autonomy hardening flow to manage plan execution through the A2A protocol. This issue blocks Epic #8423. ## Expected Behavior - `agents a2a plan create <session-id> <spec>` creates a new plan within a session - `agents a2a plan start <plan-id>` starts plan execution - `agents a2a plan status <plan-id>` shows current plan status - `agents a2a plan cancel <plan-id>` cancels a running plan ## Acceptance Criteria - [ ] `agents a2a plan create` command is registered and functional - [ ] `agents a2a plan start` command is registered and functional - [ ] `agents a2a plan status` command is registered and functional - [ ] `agents a2a plan cancel` command is registered and functional - [ ] Plan state is persisted to the database - [ ] Integration tests verify all plan lifecycle operations - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Register `a2a plan` subcommands in the CLI - [ ] Implement A2A plan create service function - [ ] Implement A2A plan start service function - [ ] Implement A2A plan status service function - [ ] Implement A2A plan cancel service function - [ ] Write integration tests for all plan lifecycle operations - [ ] Write unit tests for service functions ## Definition of Done 1. All A2A plan lifecycle CLI commands are functional 2. Integration tests verify all operations 3. Unit tests pass with >= 97% coverage 4. Code reviewed and merged to main branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.5.0 milestone 2026-04-13 20:56:31 +00:00
Author
Owner

[AUTO-OWNR-4] Triage Decision (Cycle 2)

Status: Verified

MoSCoW: Must Have
Priority: High
Milestone: v3.5.0

Rationale: This is a required implementation task for the v3.5.0 milestone (Autonomy Hardening). A2A facade plan lifecycle operations are explicitly listed in the v3.5.0 acceptance criteria under "A2A facade session and plan lifecycle operations functional via CLI."

Next Steps: Implementation worker should pick this up as part of the v3.5.0 epic work.


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

## [AUTO-OWNR-4] Triage Decision (Cycle 2) **Status**: ✅ Verified **MoSCoW**: Must Have **Priority**: High **Milestone**: v3.5.0 **Rationale**: This is a required implementation task for the v3.5.0 milestone (Autonomy Hardening). A2A facade plan lifecycle operations are explicitly listed in the v3.5.0 acceptance criteria under "A2A facade session and plan lifecycle operations functional via CLI." **Next Steps**: Implementation worker should pick this up as part of the v3.5.0 epic work. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-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.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#8543
No description provided.