reflector(a2a): execute ACP to A2A module rename and symbol standardization #11165
No reviewers
Labels
No labels
auto/needs-reevaluation
controller-managed
overdue
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cleveragents/cleveragents-core!11165
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/acp-a2a-rename-fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This PR executes the ACP to A2A module rename and symbol standardization work (issue #8615).
Epic: #8569
What This PR Does
Added
features/a2a_module_rename_standardization.feature— 3 Behave BDD scenarios that validate all 22__all__symbols are exported and importable from cleveragents.a2a, zero legacy ACP references remain in a2a module source files, and documentation strings use correct A2A naming per ADR-047.Added
features/steps/a2a_module_rename_standardization_steps.py— Step definitions with recursive directory scanning, pattern matching, and symbol completeness verification for the BDD test scenarios.Updated CHANGELOG.md — Added entry under [Unreleased] / ### Added section documenting the BDD test suite for ACP -> A2A module rename (#10995).
Updated CONTRIBUTORS.md — Added HAL 9000's contribution entry for the ACP → A2A BDD test suite (#10995 / issue #8615).
Updated
src/cleveragents/a2a/__init__.py— Added ADR-047 naming convention reference to the package docstring.PR Compliance Checklist
ISSUES CLOSED: #8615in footerCloses #8615
Closes #8569
PR Fix Attempt — Tier 1: qwen-large — Success
Fixed the CI / lint failure on PR #11165.
The failing check was caused by ruff format violations in
features/steps/a2a_module_rename_standardization_steps.py. Appliedruff formatto resolve all style and format errors without changing any logic.Quality gate status after fix:
Committed:
c91e5b11 fix(lint): apply ruff formatting to a2a_module_rename_standardization_stepsAutomated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor
Code Review — PR #11165: ACP to A2A Module Rename BDD Test Suite
CI Gate Status
All required merge gates pass on head commit
c91e5b11:The benchmark-regression failure is non-blocking per CI configuration (informational job not in the required needs list of status-check).
Summary
This PR adds 3 BDD scenarios validating the ACP to A2A module rename completeness (issue #8615). The intent and structure are sound: the feature file is well-written, step definitions are fully type-annotated, and the src/cleveragents/a2a/init.py docstring update correctly satisfies the third scenario. CHANGELOG.md and CONTRIBUTORS.md are updated correctly. The ISSUES CLOSED: #8615 footer is present in the main commit.
There are 2 blocking issues that must be resolved before approval.
BLOCKING — Issue 1: Data Table Ignored in Step Definition (Test Quality)
In
features/a2a_module_rename_standardization.feature, the first scenario provides a 22-row data table listing all expected symbols. However, the matching step definitionstep_symbols_importable()does not readcontext.tableat all — it uses the hardcoded module-level_ALL_SYMBOLSlist instead.The 22-row table in the .feature file is dead code — it is never read. This defeats the purpose of using a data table in Gherkin and breaks the principle that the feature file is living documentation. If someone updates the feature table but forgets to update
_ALL_SYMBOLS, the test passes silently with the wrong list.How to fix: Use
context.table.rowsin the step definition:This makes the feature file the single source of truth for the expected symbol list.
BLOCKING — Issue 2: Unsquashed Fixup Commits (Commit Hygiene)
The PR branch contains 3 commits:
Commits
c91e5b11and657ca1ffare fixup commits. Per CONTRIBUTING.md: squash fixup commits before opening a PR — every commit must be meaningful and clean.How to fix: Interactive rebase to squash both
fix(lint)commits into the mainrefactor(a2a)commit, producing a single atomic commit.Non-Blocking Observations
PR Title Typo — The PR title reads
reflector(a2a):— should berefactor(a2a):. Worth correcting before merge.Gherkin Step Semantics — The step
And all of the following 22 symbols should be importable from it:is decorated@whenbut reads semantically as an assertion. Minor clarity issue, does not block test execution.Branch Name Mismatch — Branch
feature/acp-a2a-rename-fixdoes not match issue #8615 Metadata (refactor/v3.6.0-acp-to-a2a-rename) nor the projectmN-convention. Cannot be renamed post-creation; noted for future discipline.Please squash the fixup commits and fix the
context.tableissue in the step definition, then re-request review.Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
@ -0,0 +95,4 @@"cleveragents.a2a must define __all__")symbols = list(_ALL_SYMBOLS)context._expected_symbols = symbolsBLOCKING — Data table is ignored; hardcoded list used instead
This step receives a 22-row data table from the feature file (via
context.table) but never reads it._ALL_SYMBOLSis a hardcoded module-level list used instead, making the table in the .feature file dead code.Problem: If someone updates the symbol table in the .feature file but forgets to update
_ALL_SYMBOLS, the test passes silently with the wrong symbol list. The Gherkin table appears to be the source of truth but is not.Fix: Replace
symbols = list(_ALL_SYMBOLS)with:This makes the feature file the authoritative symbol list, ensuring the Gherkin table and the test implementation remain in sync.
Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
Review submitted (REQUEST_CHANGES) — review ID 8717.
Findings:
features/a2a_module_rename_standardization.featureis ignored by the step definition;context.tablemust be used instead of the hardcoded_ALL_SYMBOLSlist.reflectorshould berefactor), Gherkin step semantics (@when vs @then), branch name mismatch.CI: All required gates pass.
benchmark-regressionfailure is non-blocking.Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
c91e5b114fac91b9e9a5🌱 Grooming: proceed — PR cleared for processing.
(check
no_duplicates, categoryno_duplicates)PR #11165 executes the ACP-to-A2A module rename with implementation changes (new BDD feature scenarios, updated module docstrings, CHANGELOG/CONTRIBUTORS updates). PR #10668 adds post-rename regression tests. Both address issue #8615 but serve complementary purposes: implementation vs. test coverage. No topical overlap or code duplication—both would be merged.
📋 Estimate: tier 1.
4-file change (232 additions, 211 deletions): new BDD feature file + step definitions with non-trivial logic (recursive directory scanning, pattern matching, symbol completeness verification), plus CHANGELOG/CONTRIBUTORS docs and a minimal init.py docstring update. Test-additive work with real logic in the step definitions consistently regresses at tier 0 in this codebase. Multi-file scope and non-mechanical step implementation warrant tier 1. CI is green, scope is clear, but the step definition complexity rules out tier 0.
(attempt #7, tier 1)
🔧 Implementer attempt —
rebase-failed.Blockers:
ac91b9e9a5d4adfe7f5ed4adfe7f5ebc82e34bd8✅ Approved
Reviewed at commit
bc82e34.Confidence: high.
Claimed by
merge_drive.py(pid 2329255) until2026-06-15T08:29:40.866378+00:00.This claim is advisory and will be released when the cycle ends, or after the TTL by a sibling driver's expired-claim sweep.
bc82e34bd8f83708bb34Approved by the controller reviewer stage (workflow 515).