feat: implement A2A facade plan lifecycle create/execute/apply operations #8151

Open
opened 2026-04-13 04:04:46 +00:00 by HAL9000 · 1 comment
Owner

Background and Context

After session management, the A2A facade must expose plan lifecycle operations (create, execute, apply) so that external systems can drive plan execution through the A2A protocol. This is required for the full autonomy acceptance flow.

Current Behavior

A2A facade plan lifecycle operations are not implemented. Plans cannot be created or executed through the A2A facade.

Expected Behavior

agents a2a plan create creates a plan within an A2A session. agents a2a plan execute triggers plan execution. agents a2a plan apply applies the plan results. All operations return structured A2A-compliant responses.

Acceptance Criteria

  • agents a2a plan create creates a plan within a session
  • agents a2a plan execute triggers plan execution and returns execution ID
  • agents a2a plan apply applies plan results with validation
  • All operations return A2A-compliant JSON responses
  • Plan lifecycle state transitions are correctly enforced
  • Error responses follow A2A error format
  • Test coverage >= 97% for plan lifecycle operations

Metadata

  • Commit message: feat: implement A2A facade plan lifecycle create/execute/apply
  • Branch name: feat/a2a-facade-plan-lifecycle

Subtasks

  • Implement plan create operation in A2A facade
  • Implement plan execute operation with async support
  • Implement plan apply operation with validation
  • Ensure A2A-compliant response format for all operations
  • Implement state transition enforcement
  • Write unit tests for plan lifecycle operations
  • Write integration tests for full plan lifecycle via A2A

Definition of Done

A2A facade plan create/execute/apply operations work end-to-end, return A2A-compliant responses, and test coverage >= 97%.

Parent Epic

Blocks #8082


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

## Background and Context After session management, the A2A facade must expose plan lifecycle operations (create, execute, apply) so that external systems can drive plan execution through the A2A protocol. This is required for the full autonomy acceptance flow. ## Current Behavior A2A facade plan lifecycle operations are not implemented. Plans cannot be created or executed through the A2A facade. ## Expected Behavior `agents a2a plan create` creates a plan within an A2A session. `agents a2a plan execute` triggers plan execution. `agents a2a plan apply` applies the plan results. All operations return structured A2A-compliant responses. ## Acceptance Criteria - [ ] `agents a2a plan create` creates a plan within a session - [ ] `agents a2a plan execute` triggers plan execution and returns execution ID - [ ] `agents a2a plan apply` applies plan results with validation - [ ] All operations return A2A-compliant JSON responses - [ ] Plan lifecycle state transitions are correctly enforced - [ ] Error responses follow A2A error format - [ ] Test coverage >= 97% for plan lifecycle operations ## Metadata - **Commit message**: `feat: implement A2A facade plan lifecycle create/execute/apply` - **Branch name**: `feat/a2a-facade-plan-lifecycle` ## Subtasks - [ ] Implement plan create operation in A2A facade - [ ] Implement plan execute operation with async support - [ ] Implement plan apply operation with validation - [ ] Ensure A2A-compliant response format for all operations - [ ] Implement state transition enforcement - [ ] Write unit tests for plan lifecycle operations - [ ] Write integration tests for full plan lifecycle via A2A ## Definition of Done A2A facade plan create/execute/apply operations work end-to-end, return A2A-compliant responses, and test coverage >= 97%. ## Parent Epic Blocks #8082 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.5.0 milestone 2026-04-13 04:07:41 +00:00
Author
Owner

Verified — The v3.5.0 acceptance criterion requires: 'A2A facade session and plan lifecycle operations functional via CLI.' Plan lifecycle (create/execute/apply) is the core of this requirement. Must Have for v3.5.0. Verified.


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

✅ **Verified** — The v3.5.0 acceptance criterion requires: 'A2A facade session and plan lifecycle operations functional via CLI.' Plan lifecycle (create/execute/apply) is the core of this requirement. **Must Have** for v3.5.0. Verified. --- **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#8151
No description provided.