UAT: A2aVersionNegotiator reports CURRENT_VERSION='1.0' and rejects '2.0', contradicting JSON-RPC 2.0 protocol adoption #2747

Closed
opened 2026-04-04 15:33:32 +00:00 by freemo · 7 comments
Owner

State transition confirmed: added State/In Progress; removed State/Verified.

Current state transitions:

  • Removed: State/Verified
  • Added: State/In Progress

No preconditions violated. Blocked label not present; no blocker issues referenced.


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

State transition confirmed: added State/In Progress; removed State/Verified. Current state transitions: - Removed: State/Verified - Added: State/In Progress No preconditions violated. Blocked label not present; no blocker issues referenced. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-state-updater
freemo added this to the v3.8.0 milestone 2026-04-04 15:33:44 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Medium — Internal contradiction between JSONRPC_VERSION = "2.0" in models.py and CURRENT_VERSION = "1.0" in versioning.py. Not blocking current functionality (local mode doesn't negotiate versions), but will cause failures when external clients attempt version negotiation.
  • Milestone: v3.8.0 (M9: Server Implementation)
  • MoSCoW: Must Have — Per the spec, "A2A is built on JSON-RPC 2.0". The version negotiator MUST report 2.0 as the current version. This is a protocol identity issue — the system claims to speak JSON-RPC 2.0 but the negotiator rejects it.
  • Parent Epic: #933 (A2A Protocol Compliance)

Straightforward fix — update two constants and one test scenario. Low risk, high value for protocol correctness.


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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium — Internal contradiction between `JSONRPC_VERSION = "2.0"` in models.py and `CURRENT_VERSION = "1.0"` in versioning.py. Not blocking current functionality (local mode doesn't negotiate versions), but will cause failures when external clients attempt version negotiation. - **Milestone**: v3.8.0 (M9: Server Implementation) - **MoSCoW**: Must Have — Per the spec, "A2A is built on JSON-RPC 2.0". The version negotiator MUST report 2.0 as the current version. This is a protocol identity issue — the system claims to speak JSON-RPC 2.0 but the negotiator rejects it. - **Parent Epic**: #933 (A2A Protocol Compliance) Straightforward fix — update two constants and one test scenario. Low risk, high value for protocol correctness. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
Author
Owner

Labels updated for issue #2747: Removed State/Verified; Added State/In Progress.

Preconditions checked:

  • Transitioning from State/Verified to State/In Progress (allowed per Ticket Lifecycle)
  • No Blocked label present
  • No blocker issue linked

Summary of changes:

  • Removed: State/Verified
  • Added: State/In Progress

If there are any blockers or additional transitions required, please let me know.


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

Labels updated for issue #2747: Removed State/Verified; Added State/In Progress. Preconditions checked: - Transitioning from State/Verified to State/In Progress (allowed per Ticket Lifecycle) - No Blocked label present - No blocker issue linked Summary of changes: - Removed: State/Verified - Added: State/In Progress If there are any blockers or additional transitions required, please let me know. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-state-updater
Author
Owner

Starting implementation on branch fix/a2a-version-negotiator-jsonrpc-2-0.

Plan: This is a straightforward fix with all subtasks independent (no inter-subtask dependencies):

  • Wave 1 (parallel): Update versioning.py constants + update consolidated_misc.feature test scenario + scan for any other tests asserting CURRENT_VERSION == "1.0"
  • Wave 2: Run nox quality gates (typecheck, unit_tests, coverage_report)

Difficulty assessment: Low → starting at sonnet tier.


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

Starting implementation on branch `fix/a2a-version-negotiator-jsonrpc-2-0`. **Plan:** This is a straightforward fix with all subtasks independent (no inter-subtask dependencies): - Wave 1 (parallel): Update `versioning.py` constants + update `consolidated_misc.feature` test scenario + scan for any other tests asserting `CURRENT_VERSION == "1.0"` - Wave 2: Run nox quality gates (typecheck, unit_tests, coverage_report) Difficulty assessment: Low → starting at sonnet tier. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
freemo referenced this issue from a commit 2026-04-05 08:41:39 +00:00
```
Author
Owner

State transition confirmed: added State/In Review; removed State/Verified.

Current state transitions:

  • Removed: State/Verified
  • Added: State/In Review

PR #3285 has been opened for this issue: #3285

No preconditions violated. Blocked label not present; no blocker issues referenced.


Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-pr-api-creator

State transition confirmed: added State/In Review; removed State/Verified. Current state transitions: - Removed: State/Verified - Added: State/In Review PR #3285 has been opened for this issue: https://git.cleverthis.com/cleveragents/cleveragents-core/pulls/3285 No preconditions violated. Blocked label not present; no blocker issues referenced. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-pr-api-creator
Author
Owner

All subtasks complete. Quality gates passed (typecheck: 0 errors, unit_tests: 250 scenarios passed). Creating PR.

PR #3285 created on branch fix/a2a-version-negotiator-jsonrpc-2-0. PR review and merge handled by continuous review stream.

Implementation summary:

  • A2aVersionNegotiator.CURRENT_VERSION: "1.0""2.0"
  • A2aVersionNegotiator.SUPPORTED_VERSIONS: ("1.0",)("2.0",)
  • 7 Behave scenarios updated in features/consolidated_misc.feature

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

All subtasks complete. Quality gates passed (typecheck: 0 errors, unit_tests: 250 scenarios passed). Creating PR. PR #3285 created on branch `fix/a2a-version-negotiator-jsonrpc-2-0`. PR review and merge handled by continuous review stream. **Implementation summary:** - `A2aVersionNegotiator.CURRENT_VERSION`: `"1.0"` → `"2.0"` - `A2aVersionNegotiator.SUPPORTED_VERSIONS`: `("1.0",)` → `("2.0",)` - 7 Behave scenarios updated in `features/consolidated_misc.feature` --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
Author
Owner

Issue Body Compliance Problem: This issue's body contains only a state transition log instead of the actual issue description.

Per CONTRIBUTING.md, every issue body must contain:

  • ## Metadata section (with Branch and Commit Message)
  • ## Subtasks section (with at least one checkbox)
  • ## Definition of Done section

The original issue description for A2aVersionNegotiator CURRENT_VERSION appears to have been overwritten. Please restore the original issue description.


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

**Issue Body Compliance Problem:** This issue's body contains only a state transition log instead of the actual issue description. Per CONTRIBUTING.md, every issue body must contain: - `## Metadata` section (with Branch and Commit Message) - `## Subtasks` section (with at least one checkbox) - `## Definition of Done` section The original issue description for `A2aVersionNegotiator CURRENT_VERSION` appears to have been overwritten. Please restore the original issue description. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
Owner

State label reconciliation:

  • Corrected to: State/Completed
  • Reason: Issue is closed but had a non-terminal state label (State/In Review, State/Verified, or State/In Progress). CONTRIBUTING.md requires closed issues to have State/Completed or State/Wont Do.

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

State label reconciliation: - Corrected to: `State/Completed` - Reason: Issue is closed but had a non-terminal state label (`State/In Review`, `State/Verified`, or `State/In Progress`). CONTRIBUTING.md requires closed issues to have `State/Completed` or `State/Wont Do`. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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#2747
No description provided.