BUG-HUNT: [spec-alignment] Missing standard A2A operations in A2aLocalFacade #1947

Closed
opened 2026-04-03 00:20:29 +00:00 by freemo · 4 comments
Owner

Transitioned issue to State/Verified from State/Unverified as part of the Ticket Lifecycle.

Transitioned issue to State/Verified from State/Unverified as part of the Ticket Lifecycle.
freemo added this to the v3.5.0 milestone 2026-04-03 00:21:03 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — the A2A facade is missing all standard A2A operations (message/send, message/stream, tasks/get, tasks/list, tasks/cancel, getExtendedAgentCard). This is a fundamental spec-alignment gap per ADR-047.
  • Milestone: v3.5.0 (already assigned, correct — A2A facade operations are a core M6 Autonomy Hardening acceptance criterion)
  • MoSCoW: Must Have — the v3.5.0 acceptance criteria explicitly require "A2A facade session and plan lifecycle operations functional via CLI." Without standard A2A operations, the facade is non-compliant with the protocol standard adopted in ADR-047.
  • Parent Epic: #933 (A2A Protocol Compliance)

This is a large issue covering 6 distinct operations. It may benefit from being broken into sub-issues per operation, but the current structure with subtasks is acceptable for tracking.


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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — the A2A facade is missing all standard A2A operations (`message/send`, `message/stream`, `tasks/get`, `tasks/list`, `tasks/cancel`, `getExtendedAgentCard`). This is a fundamental spec-alignment gap per ADR-047. - **Milestone**: v3.5.0 (already assigned, correct — A2A facade operations are a core M6 Autonomy Hardening acceptance criterion) - **MoSCoW**: Must Have — the v3.5.0 acceptance criteria explicitly require "A2A facade session and plan lifecycle operations functional via CLI." Without standard A2A operations, the facade is non-compliant with the protocol standard adopted in ADR-047. - **Parent Epic**: #933 (A2A Protocol Compliance) This is a large issue covering 6 distinct operations. It may benefit from being broken into sub-issues per operation, but the current structure with subtasks is acceptable for tracking. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Author
Owner

Transition attempt: State/Unverified -> State/Verified for issue #1947. Current labels: Priority/High, State/Unverified, Type/Bug. Attempted removal of State/Unverified and addition of State/Verified. Milestone set to v3.5.0 (ID 108). Result: labels not updated. Will retry or adjust approach if needed.


Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-state-updater

Transition attempt: State/Unverified -> State/Verified for issue #1947. Current labels: Priority/High, State/Unverified, Type/Bug. Attempted removal of State/Unverified and addition of State/Verified. Milestone set to v3.5.0 (ID 108). Result: labels not updated. Will retry or adjust approach if needed. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-state-updater
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High (unchanged)
  • Milestone: v3.5.0 (already assigned — milestone is past due)
  • MoSCoW: Must Have — Missing standard A2A operations in A2aLocalFacade is a spec-alignment issue. The specification mandates A2A protocol compliance, and the local facade must implement all standard operations. This is tracked under Epic #933 (A2A Protocol Compliance).

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

Issue triaged by project owner: - **State**: Verified ✅ - **Priority**: High (unchanged) - **Milestone**: v3.5.0 (already assigned — milestone is past due) - **MoSCoW**: Must Have — Missing standard A2A operations in `A2aLocalFacade` is a spec-alignment issue. The specification mandates A2A protocol compliance, and the local facade must implement all standard operations. This is tracked under Epic #933 (A2A Protocol Compliance). --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Author
Owner

Closing as duplicate of #2569.

Both issues describe the same bug: A2aLocalFacade is missing standard A2A operations (message/send, message/stream). Issue #2569 is the established tracking issue (v3.8.0 milestone, Priority/High, State/Verified). Please track this work in #2569.


Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Closing as duplicate of #2569. Both issues describe the same bug: `A2aLocalFacade` is missing standard A2A operations (`message/send`, `message/stream`). Issue #2569 is the established tracking issue (v3.8.0 milestone, `Priority/High`, `State/Verified`). Please track this work in #2569. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
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#1947
No description provided.