Epic: ACP to A2A Module Rename & Symbol Standardization (M7) #8085

Open
opened 2026-04-13 03:27:50 +00:00 by HAL9000 · 3 comments
Owner

Metadata

  • Commit message: refactor: rename ACP module references to A2A per ADR-047
  • Branch name: refactor/acp-to-a2a-module-rename-symbol-standardization

Background and Context

Following ADR-047 (A2A Standard Adoption), all ACP module references must be renamed to A2A across the entire codebase. This is a cross-cutting refactor that affects imports, CLI commands, documentation, and test fixtures. Consistency in naming is critical for developer experience and for compliance with the A2A standard.

The mixed ACP/A2A naming in the current codebase creates confusion for contributors and users alike. It also breaks tooling that relies on consistent module naming for auto-discovery and documentation generation. This refactor must be completed in M7 before further A2A-dependent features are built on top of the inconsistent naming.

The rename must be done carefully to avoid breaking existing integrations. A thorough audit of all ACP references must precede the rename, and the full test suite must pass after the rename to confirm no regressions were introduced.

Current Behavior

Codebase uses mixed ACP/A2A naming. Some modules use acp, others use a2a. This causes confusion and breaks the A2A standard adoption. CLI commands, imports, documentation, and test fixtures are inconsistent in their use of ACP vs A2A terminology.

Expected Behavior

All ACP references are renamed to A2A. Imports, CLI commands, documentation, and test fixtures use consistent A2A naming. No ACP references remain in the codebase (except migration notes). All existing tests pass after the rename.

Acceptance Criteria

  • All acp module imports renamed to a2a
  • All CLI commands using acp renamed to a2a
  • All documentation updated to use A2A terminology
  • All test fixtures updated to use A2A naming
  • No acp references remain in source code (except migration notes)
  • All existing tests pass after rename
  • All child issues are closed and merged

Subtasks

  • Audit all ACP references in source code
  • Rename ACP module imports to A2A
  • Rename ACP CLI commands to A2A
  • Update documentation to use A2A terminology
  • Update test fixtures to use A2A naming
  • Run full test suite to verify no regressions

Child Issues

  • #8885 — Refactor: Unify API Naming Conventions and Method Signatures
  • #8880 — Refactor: Decouple CLI from Application Services
  • #8867 — Refactor: Unify Service Initialization and Dependency Injection
  • #8857 — Refactor: Unify Error Handling and User Feedback in CLI

Parent Legendary

Parent Legendary: #8504 (Legendary: Advanced Concepts & Platform Extensions (v3.6.0))

Definition of Done

Epic complete when all ACP references are renamed to A2A across source code, CLI, documentation, and test fixtures, and the full test suite passes with no regressions.


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

## Metadata - **Commit message**: `refactor: rename ACP module references to A2A per ADR-047` - **Branch name**: `refactor/acp-to-a2a-module-rename-symbol-standardization` ## Background and Context Following ADR-047 (A2A Standard Adoption), all ACP module references must be renamed to A2A across the entire codebase. This is a cross-cutting refactor that affects imports, CLI commands, documentation, and test fixtures. Consistency in naming is critical for developer experience and for compliance with the A2A standard. The mixed ACP/A2A naming in the current codebase creates confusion for contributors and users alike. It also breaks tooling that relies on consistent module naming for auto-discovery and documentation generation. This refactor must be completed in M7 before further A2A-dependent features are built on top of the inconsistent naming. The rename must be done carefully to avoid breaking existing integrations. A thorough audit of all ACP references must precede the rename, and the full test suite must pass after the rename to confirm no regressions were introduced. ## Current Behavior Codebase uses mixed ACP/A2A naming. Some modules use `acp`, others use `a2a`. This causes confusion and breaks the A2A standard adoption. CLI commands, imports, documentation, and test fixtures are inconsistent in their use of ACP vs A2A terminology. ## Expected Behavior All ACP references are renamed to A2A. Imports, CLI commands, documentation, and test fixtures use consistent A2A naming. No ACP references remain in the codebase (except migration notes). All existing tests pass after the rename. ## Acceptance Criteria - [ ] All `acp` module imports renamed to `a2a` - [ ] All CLI commands using `acp` renamed to `a2a` - [ ] All documentation updated to use A2A terminology - [ ] All test fixtures updated to use A2A naming - [ ] No `acp` references remain in source code (except migration notes) - [ ] All existing tests pass after rename - [ ] All child issues are closed and merged ## Subtasks - [ ] Audit all ACP references in source code - [ ] Rename ACP module imports to A2A - [ ] Rename ACP CLI commands to A2A - [ ] Update documentation to use A2A terminology - [ ] Update test fixtures to use A2A naming - [ ] Run full test suite to verify no regressions ## Child Issues - #8885 — Refactor: Unify API Naming Conventions and Method Signatures - #8880 — Refactor: Decouple CLI from Application Services - #8867 — Refactor: Unify Service Initialization and Dependency Injection - #8857 — Refactor: Unify Error Handling and User Feedback in CLI ## Parent Legendary **Parent Legendary**: #8504 (Legendary: Advanced Concepts & Platform Extensions (v3.6.0)) ## Definition of Done Epic complete when all ACP references are renamed to A2A across source code, CLI, documentation, and test fixtures, and the full test suite passes with no regressions. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.6.0 milestone 2026-04-13 03:28:30 +00:00
Author
Owner

[AUTO-OWNR-1] Triage Decision

Status: Verified

MoSCoW Priority: Must Have

Rationale: ADR-047 elevates the ACP→A2A rename to prerequisite status; without the standardization the rest of the M7 A2A work and tooling integrations cannot proceed safely.

Milestone: v3.6.0 — M7: Advanced Concepts & Deferred Features

This issue has been reviewed and verified by the project owner. It is now ready for development.


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

## [AUTO-OWNR-1] Triage Decision **Status**: ✅ Verified **MoSCoW Priority**: Must Have **Rationale**: ADR-047 elevates the ACP→A2A rename to prerequisite status; without the standardization the rest of the M7 A2A work and tooling integrations cannot proceed safely. **Milestone**: v3.6.0 — M7: Advanced Concepts & Deferred Features This issue has been reviewed and verified by the project owner. It is now ready for development. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
Author
Owner

[AUTO-EPIC] Parent Legendary Linkage Update

Parent Legendary identified: #8134 — Legendary: Advanced Concepts & Platform Extensions (v3.6.0)

The Epic body previously noted "Parent Legendary: TBD". The correct parent is #8134.

Dependency direction: This Epic (#8085) BLOCKS Legendary #8134. Legendary #8134 DEPENDS ON this Epic.


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

## [AUTO-EPIC] Parent Legendary Linkage Update **Parent Legendary identified**: #8134 — Legendary: Advanced Concepts & Platform Extensions (v3.6.0) The Epic body previously noted "Parent Legendary: TBD". The correct parent is #8134. **Dependency direction**: This Epic (#8085) BLOCKS Legendary #8134. Legendary #8134 DEPENDS ON this Epic. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Author
Owner

🧩 Child Implementation Issues Created

The following child issues have been created for this Epic and are now tracked under milestone v3.6.0:

# Issue Priority Branch
1 #8206 — refactor: audit and rename all ACP module imports to A2A per ADR-047 🟠 High refactor/acp-to-a2a-module-imports
2 #8207 — refactor: rename all ACP CLI commands to A2A for consistent user-facing interface 🟠 High refactor/acp-to-a2a-cli-commands
3 #8208 — refactor: update all documentation and test fixtures to use A2A naming per ADR-047 🟠 High refactor/acp-to-a2a-docs-test-fixtures

All 3 child issues block this Epic and must be completed before this Epic can be closed.


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

## 🧩 Child Implementation Issues Created The following child issues have been created for this Epic and are now tracked under milestone **v3.6.0**: | # | Issue | Priority | Branch | |---|-------|----------|--------| | 1 | #8206 — refactor: audit and rename all ACP module imports to A2A per ADR-047 | 🟠 High | `refactor/acp-to-a2a-module-imports` | | 2 | #8207 — refactor: rename all ACP CLI commands to A2A for consistent user-facing interface | 🟠 High | `refactor/acp-to-a2a-cli-commands` | | 3 | #8208 — refactor: update all documentation and test fixtures to use A2A naming per ADR-047 | 🟠 High | `refactor/acp-to-a2a-docs-test-fixtures` | All 3 child issues block this Epic and must be completed before this Epic can be closed. --- **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.

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