refactor: update all documentation and test fixtures to use A2A naming per ADR-047 #8208

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

Background and Context

The ACP to A2A rename must be complete across documentation and test fixtures, not just source code. Inconsistent naming in documentation confuses users and contributors. Test fixtures using old ACP naming will fail after the source code rename, so they must be updated in sync.

Current Behavior

Documentation and test fixtures use mixed ACP/A2A naming. Some docs reference acp commands and modules. Test fixtures use acp naming that will break after source code rename.

Expected Behavior

All documentation uses A2A terminology consistently. All test fixtures use A2A naming. No ACP references remain in documentation or test fixtures (except migration notes). The full test suite passes with updated fixtures.

Acceptance Criteria

  • All documentation updated to use A2A terminology
  • All test fixtures updated to use A2A naming
  • No ACP references remain in documentation or test fixtures
  • Full test suite passes with updated fixtures
  • Migration guide documents the ACP → A2A rename for users
  • Test coverage >= 97% maintained after updates

Metadata

  • Commit Message: refactor: update documentation and test fixtures to A2A naming
  • Branch Name: refactor/acp-to-a2a-docs-test-fixtures

Subtasks

  • Audit all documentation for ACP references
  • Update documentation to use A2A terminology
  • Audit all test fixtures for ACP naming
  • Update test fixtures to use A2A naming
  • Write migration guide for ACP → A2A rename
  • Run full test suite to verify no regressions

Definition of Done

All documentation and test fixtures use A2A naming, migration guide is written, and test coverage >= 97% maintained.

Parent Epic

Child of and blocks #8085 — ACP to A2A Module Rename & Symbol Standardization


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

## Background and Context The ACP to A2A rename must be complete across documentation and test fixtures, not just source code. Inconsistent naming in documentation confuses users and contributors. Test fixtures using old ACP naming will fail after the source code rename, so they must be updated in sync. ## Current Behavior Documentation and test fixtures use mixed ACP/A2A naming. Some docs reference `acp` commands and modules. Test fixtures use `acp` naming that will break after source code rename. ## Expected Behavior All documentation uses A2A terminology consistently. All test fixtures use A2A naming. No ACP references remain in documentation or test fixtures (except migration notes). The full test suite passes with updated fixtures. ## Acceptance Criteria - [ ] All documentation updated to use A2A terminology - [ ] All test fixtures updated to use A2A naming - [ ] No ACP references remain in documentation or test fixtures - [ ] Full test suite passes with updated fixtures - [ ] Migration guide documents the ACP → A2A rename for users - [ ] Test coverage >= 97% maintained after updates ## Metadata - **Commit Message**: `refactor: update documentation and test fixtures to A2A naming` - **Branch Name**: `refactor/acp-to-a2a-docs-test-fixtures` ## Subtasks - [ ] Audit all documentation for ACP references - [ ] Update documentation to use A2A terminology - [ ] Audit all test fixtures for ACP naming - [ ] Update test fixtures to use A2A naming - [ ] Write migration guide for ACP → A2A rename - [ ] Run full test suite to verify no regressions ## Definition of Done All documentation and test fixtures use A2A naming, migration guide is written, and test coverage >= 97% maintained. ## Parent Epic Child of and blocks #8085 — ACP to A2A Module Rename & Symbol Standardization --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.6.0 milestone 2026-04-13 04:28:54 +00:00
Author
Owner

Verified — Documentation and test fixture updates are required to complete the ACP→A2A rename per ADR-047. Without this, docs and tests would be inconsistent with the implementation. Must Have for v3.6.0. Verified.


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

✅ **Verified** — Documentation and test fixture updates are required to complete the ACP→A2A rename per ADR-047. Without this, docs and tests would be inconsistent with the implementation. **Must Have** for v3.6.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#8208
No description provided.