cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

fix(a2a): change A2aErrorDetail.code to int and map error constants to JSON-RPC 2.0 integer codes #3310

Merged
freemo merged 1 commits from fix/a2a-error-codes-integer-jsonrpc2 into master 2026-04-05 21:10:19 +00:00
Conversation 5 Commits 1 Files Changed 10
+130 -31
freemo commented 2026-04-05 09:35:22 +00:00
Owner
Copy Link
Copy Source

Summary

Fixes #2746 — A2aErrorDetail.code was typed as str and error constants were string literals, violating the JSON-RPC 2.0 specification which requires error codes to be integers.

Problem

External A2A-compliant clients received {"code": "NOT_FOUND", ...} instead of the required {"code": -32001, ...}, breaking interoperability with any standards-conformant JSON-RPC 2.0 client.

Changes

Core Type Fix

  • src/cleveragents/a2a/models.py: Changed A2aErrorDetail.code from str to int; updated field_validator to only validate message field (Pydantic enforces int type for code)
  • src/cleveragents/a2a/errors.py: Changed all error code constants from string literals to JSON-RPC 2.0 integer codes per docs/reference/a2a.md taxonomy:
    • NOT_FOUND = -32001
    • AUTH_ERROR = -32002
    • FORBIDDEN = -32003
    • INVALID_STATE = -32004
    • PLAN_ERROR = -32008
    • CONFIGURATION_ERROR = -32009
    • VALIDATION_ERROR = -32602
    • INTERNAL_ERROR = -32603
  • Updated map_domain_error() return type from tuple[str, str] to tuple[int, str]

Test Updates

  • features/steps/a2a_facade_steps.py: Updated A2aErrorDetail construction to map symbolic string names to integer codes via _CODE_MAP
  • features/steps/a2a_facade_wiring_steps.py: Updated error code assertion to map symbolic names to integers for comparison
  • features/steps/a2a_facade_coverage_boost_steps.py: Same as above
  • features/steps/a2a_jsonrpc_wire_format_steps.py: Updated all A2aErrorDetail constructions and JSON-RPC dict payloads to use integer codes
  • robot/helper_a2a_facade_wiring.py: Updated wired_error_mapping() to compare against integer codes
  • robot/helper_a2a_jsonrpc_wire_format.py: Updated response_error_wire_format() to use integer code -32001 instead of string "NOT_FOUND"

Design Decisions

  1. Backward-compatible step definitions: Feature files continue to use symbolic names like "NOT_FOUND" in Gherkin scenarios. Step definitions map these to integer codes via _CODE_MAP, avoiding mass feature file changes while maintaining readability.

  2. Integer taxonomy follows spec: The integer values follow the JSON-RPC 2.0 standard codes (-32700 to -32600) for standard errors, and the application-defined range (-32001 to -32009) for domain-specific errors as documented in docs/reference/a2a.md.

  3. CONFIGURATION_ERROR assigned -32009: Not in the standard JSON-RPC 2.0 range but follows the application-defined pattern from the spec taxonomy.

Quality Gates

  • nox -e typecheck: ✅ 0 errors, 0 warnings
  • Ruff linting: ✅ No violations
  • Manual verification: All 8 test scenarios pass

Closes #2746

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

## Summary Fixes #2746 — `A2aErrorDetail.code` was typed as `str` and error constants were string literals, violating the JSON-RPC 2.0 specification which requires error codes to be integers. ## Problem External A2A-compliant clients received `{"code": "NOT_FOUND", ...}` instead of the required `{"code": -32001, ...}`, breaking interoperability with any standards-conformant JSON-RPC 2.0 client. ## Changes ### Core Type Fix - **`src/cleveragents/a2a/models.py`**: Changed `A2aErrorDetail.code` from `str` to `int`; updated `field_validator` to only validate `message` field (Pydantic enforces int type for `code`) - **`src/cleveragents/a2a/errors.py`**: Changed all error code constants from string literals to JSON-RPC 2.0 integer codes per `docs/reference/a2a.md` taxonomy: - `NOT_FOUND = -32001` - `AUTH_ERROR = -32002` - `FORBIDDEN = -32003` - `INVALID_STATE = -32004` - `PLAN_ERROR = -32008` - `CONFIGURATION_ERROR = -32009` - `VALIDATION_ERROR = -32602` - `INTERNAL_ERROR = -32603` - Updated `map_domain_error()` return type from `tuple[str, str]` to `tuple[int, str]` ### Test Updates - **`features/steps/a2a_facade_steps.py`**: Updated `A2aErrorDetail` construction to map symbolic string names to integer codes via `_CODE_MAP` - **`features/steps/a2a_facade_wiring_steps.py`**: Updated error code assertion to map symbolic names to integers for comparison - **`features/steps/a2a_facade_coverage_boost_steps.py`**: Same as above - **`features/steps/a2a_jsonrpc_wire_format_steps.py`**: Updated all `A2aErrorDetail` constructions and JSON-RPC dict payloads to use integer codes - **`robot/helper_a2a_facade_wiring.py`**: Updated `wired_error_mapping()` to compare against integer codes - **`robot/helper_a2a_jsonrpc_wire_format.py`**: Updated `response_error_wire_format()` to use integer code `-32001` instead of string `"NOT_FOUND"` ## Design Decisions 1. **Backward-compatible step definitions**: Feature files continue to use symbolic names like `"NOT_FOUND"` in Gherkin scenarios. Step definitions map these to integer codes via `_CODE_MAP`, avoiding mass feature file changes while maintaining readability. 2. **Integer taxonomy follows spec**: The integer values follow the JSON-RPC 2.0 standard codes (-32700 to -32600) for standard errors, and the application-defined range (-32001 to -32009) for domain-specific errors as documented in `docs/reference/a2a.md`. 3. **`CONFIGURATION_ERROR` assigned -32009**: Not in the standard JSON-RPC 2.0 range but follows the application-defined pattern from the spec taxonomy. ## Quality Gates - `nox -e typecheck`: ✅ 0 errors, 0 warnings - Ruff linting: ✅ No violations - Manual verification: All 8 test scenarios pass Closes #2746 --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
freemo added this to the v3.8.0 milestone 2026-04-05 09:35:22 +00:00
freemo commented 2026-04-05 10:17:42 +00:00
Author
Owner
Copy Link
Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3310-1775375100]

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3310-1775375100] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
freemo commented 2026-04-05 16:23:07 +00:00
Author
Owner
Copy Link
Copy Source

🔍 Code Review — REQUEST CHANGES

Reviewed PR #3310 with focus on test-coverage-quality, test-scenario-completeness, and test-maintainability.

The core change — converting A2aErrorDetail.code from str to int and mapping error constants to JSON-RPC 2.0 integer codes — is correct and well-motivated. The JSON-RPC 2.0 specification (Section 5.1) requires error codes to be integers, and this fix brings the implementation into compliance. The integer values chosen align with the taxonomy documented in docs/reference/a2a.md.

However, I found issues in test maintainability and spec alignment that should be addressed before merge.

Required Changes

1. [TEST-MAINTAINABILITY] _CODE_MAP duplicated 6 times across 4 step files

  • Locations:

    • features/steps/a2a_facade_steps.py — defined twice (in step_create_response and step_create_error_detail)
    • features/steps/a2a_facade_wiring_steps.py — defined once (in step_wired_error_code)
    • features/steps/a2a_facade_coverage_boost_steps.py — defined once (in step_cb_error_code)
    • features/steps/a2a_jsonrpc_wire_format_steps.py — defined twice (in step_create_error_response and step_jsonrpc_error_response_dict)

  • Issue: The identical _CODE_MAP dictionary mapping symbolic error names to integer codes is copy-pasted 6 times. If a new error code is added (e.g., -32005 for DuplicateEntityError, which is already in the spec but not in the constants), or an existing code value changes, all 6 copies must be updated in lockstep. This is a high-risk maintenance burden and violates DRY principles.

  • Required: Extract _CODE_MAP to a single shared location. Options:

    • A module-level constant in a shared test helper (e.g., features/steps/_a2a_test_helpers.py)
    • Or better yet, derive it programmatically from the cleveragents.a2a.errors module constants, e.g.: 
      # features/steps/_a2a_code_map.py
from cleveragents.a2a import errors as _a2a_errors

A2A_CODE_MAP: dict[str, int] = {
    name: getattr(_a2a_errors, name)
    for name in ("NOT_FOUND", "VALIDATION_ERROR", "INVALID_STATE",
                 "PLAN_ERROR", "AUTH_ERROR", "FORBIDDEN",
                 "CONFIGURATION_ERROR", "INTERNAL_ERROR")
}

    Then import and use this single definition in all step files.

2. [SPEC] CONFIGURATION_ERROR = -32009 not documented in docs/reference/a2a.md

  • Location: src/cleveragents/a2a/errors.py — CONFIGURATION_ERROR: int = -32009
  • Issue: The PR description states the integer codes follow "docs/reference/a2a.md taxonomy," but the Error Code Taxonomy table in docs/reference/a2a.md only goes up to -32008 (PlanError). The code -32009 for ConfigurationError is not listed in the spec reference. This creates a discrepancy between the code and the specification — which per project rules is the source of truth.
  • Required: Either:
    • (a) Add -32009 | ConfigurationError | Configuration error to the Error Code Taxonomy table in docs/reference/a2a.md, OR
    • (b) If this code assignment needs broader discussion, file a follow-up issue and add a TODO comment in the code referencing it.

Non-blocking Suggestions

3. [TEST-COVERAGE] Missing test coverage for AuthenticationError, AuthorizationError, and ConfigurationError mappings

The wired_error_mapping() function in robot/helper_a2a_facade_wiring.py tests the mapping for ResourceNotFoundError, ValidationError, PlanError, and BusinessRuleViolation, but does not test AuthenticationError → AUTH_ERROR (-32002), AuthorizationError → FORBIDDEN (-32003), or ConfigurationError → CONFIGURATION_ERROR (-32009). Similarly, the Behave wiring steps only exercise NOT_FOUND, VALIDATION_ERROR, PLAN_ERROR, and INVALID_STATE error paths. Consider adding scenarios for the remaining mappings to ensure complete coverage of the map_domain_error() function.

4. [TEST-QUALITY] Silent fallback in _CODE_MAP.get() could mask test bugs

In several step definitions, the fallback _CODE_MAP.get(code, _a2a_errors.INTERNAL_ERROR) silently maps any unknown symbolic name to INTERNAL_ERROR. If a feature file has a typo (e.g., "NOTFOUND" instead of "NOT_FOUND"), the test would silently use -32603 instead of failing. Consider using a strict lookup that raises KeyError for unknown names, or at minimum logging a warning.

5. [TEST-QUALITY] Pre-existing # type: ignore comments in test files

features/steps/a2a_facade_wiring_steps.py and features/steps/a2a_jsonrpc_wire_format_steps.py contain # type: ignore[assignment,misc] in their ImportError fallback blocks. Per CONTRIBUTING.md, # type: ignore suppressions are forbidden. These are pre-existing (not introduced by this PR), but worth noting for a follow-up cleanup.

Good Aspects

  • ✅ Backward-compatible Gherkin: Feature files continue to use human-readable symbolic names ("NOT_FOUND") while step definitions handle the mapping — excellent for test readability
  • ✅ Comprehensive file coverage: All 8 affected files (2 source, 4 Behave step files, 2 Robot helpers) are updated consistently
  • ✅ Correct JSON-RPC 2.0 compliance: Integer codes match the standard taxonomy
  • ✅ Proper Pydantic integration: Removing code from the field_validator is correct since Pydantic enforces int type natively
  • ✅ Well-structured commit: Single atomic commit with detailed message following Conventional Changelog format
  • ✅ PR metadata complete: Closing keyword, milestone, Type/Bug label all present

Decision: REQUEST CHANGES 🔄

The two required changes (extracting duplicated _CODE_MAP and documenting -32009 in the spec) should be addressed before merge. The core implementation is sound.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

## 🔍 Code Review — REQUEST CHANGES Reviewed PR #3310 with focus on **test-coverage-quality**, **test-scenario-completeness**, and **test-maintainability**. The core change — converting `A2aErrorDetail.code` from `str` to `int` and mapping error constants to JSON-RPC 2.0 integer codes — is correct and well-motivated. The JSON-RPC 2.0 specification (Section 5.1) requires error codes to be integers, and this fix brings the implementation into compliance. The integer values chosen align with the taxonomy documented in `docs/reference/a2a.md`. However, I found issues in test maintainability and spec alignment that should be addressed before merge. --- ### Required Changes #### 1. **[TEST-MAINTAINABILITY] `_CODE_MAP` duplicated 6 times across 4 step files** - **Locations:** - `features/steps/a2a_facade_steps.py` — defined twice (in `step_create_response` and `step_create_error_detail`) - `features/steps/a2a_facade_wiring_steps.py` — defined once (in `step_wired_error_code`) - `features/steps/a2a_facade_coverage_boost_steps.py` — defined once (in `step_cb_error_code`) - `features/steps/a2a_jsonrpc_wire_format_steps.py` — defined twice (in `step_create_error_response` and `step_jsonrpc_error_response_dict`) - **Issue:** The identical `_CODE_MAP` dictionary mapping symbolic error names to integer codes is copy-pasted 6 times. If a new error code is added (e.g., `-32005` for `DuplicateEntityError`, which is already in the spec but not in the constants), or an existing code value changes, all 6 copies must be updated in lockstep. This is a high-risk maintenance burden and violates DRY principles. - **Required:** Extract `_CODE_MAP` to a single shared location. Options: - A module-level constant in a shared test helper (e.g., `features/steps/_a2a_test_helpers.py`) - Or better yet, derive it programmatically from the `cleveragents.a2a.errors` module constants, e.g.: ```python # features/steps/_a2a_code_map.py from cleveragents.a2a import errors as _a2a_errors A2A_CODE_MAP: dict[str, int] = { name: getattr(_a2a_errors, name) for name in ("NOT_FOUND", "VALIDATION_ERROR", "INVALID_STATE", "PLAN_ERROR", "AUTH_ERROR", "FORBIDDEN", "CONFIGURATION_ERROR", "INTERNAL_ERROR") } ``` Then import and use this single definition in all step files. #### 2. **[SPEC] `CONFIGURATION_ERROR = -32009` not documented in `docs/reference/a2a.md`** - **Location:** `src/cleveragents/a2a/errors.py` — `CONFIGURATION_ERROR: int = -32009` - **Issue:** The PR description states the integer codes follow "docs/reference/a2a.md taxonomy," but the Error Code Taxonomy table in `docs/reference/a2a.md` only goes up to `-32008` (PlanError). The code `-32009` for `ConfigurationError` is not listed in the spec reference. This creates a discrepancy between the code and the specification — which per project rules is the source of truth. - **Required:** Either: - (a) Add `-32009 | ConfigurationError | Configuration error` to the Error Code Taxonomy table in `docs/reference/a2a.md`, OR - (b) If this code assignment needs broader discussion, file a follow-up issue and add a TODO comment in the code referencing it. --- ### Non-blocking Suggestions #### 3. **[TEST-COVERAGE] Missing test coverage for `AuthenticationError`, `AuthorizationError`, and `ConfigurationError` mappings** The `wired_error_mapping()` function in `robot/helper_a2a_facade_wiring.py` tests the mapping for `ResourceNotFoundError`, `ValidationError`, `PlanError`, and `BusinessRuleViolation`, but does **not** test `AuthenticationError → AUTH_ERROR (-32002)`, `AuthorizationError → FORBIDDEN (-32003)`, or `ConfigurationError → CONFIGURATION_ERROR (-32009)`. Similarly, the Behave wiring steps only exercise NOT_FOUND, VALIDATION_ERROR, PLAN_ERROR, and INVALID_STATE error paths. Consider adding scenarios for the remaining mappings to ensure complete coverage of the `map_domain_error()` function. #### 4. **[TEST-QUALITY] Silent fallback in `_CODE_MAP.get()` could mask test bugs** In several step definitions, the fallback `_CODE_MAP.get(code, _a2a_errors.INTERNAL_ERROR)` silently maps any unknown symbolic name to `INTERNAL_ERROR`. If a feature file has a typo (e.g., `"NOTFOUND"` instead of `"NOT_FOUND"`), the test would silently use `-32603` instead of failing. Consider using a strict lookup that raises `KeyError` for unknown names, or at minimum logging a warning. #### 5. **[TEST-QUALITY] Pre-existing `# type: ignore` comments in test files** `features/steps/a2a_facade_wiring_steps.py` and `features/steps/a2a_jsonrpc_wire_format_steps.py` contain `# type: ignore[assignment,misc]` in their `ImportError` fallback blocks. Per CONTRIBUTING.md, `# type: ignore` suppressions are forbidden. These are pre-existing (not introduced by this PR), but worth noting for a follow-up cleanup. --- ### Good Aspects - ✅ **Backward-compatible Gherkin**: Feature files continue to use human-readable symbolic names (`"NOT_FOUND"`) while step definitions handle the mapping — excellent for test readability - ✅ **Comprehensive file coverage**: All 8 affected files (2 source, 4 Behave step files, 2 Robot helpers) are updated consistently - ✅ **Correct JSON-RPC 2.0 compliance**: Integer codes match the standard taxonomy - ✅ **Proper Pydantic integration**: Removing `code` from the `field_validator` is correct since Pydantic enforces `int` type natively - ✅ **Well-structured commit**: Single atomic commit with detailed message following Conventional Changelog format - ✅ **PR metadata complete**: Closing keyword, milestone, Type/Bug label all present **Decision: REQUEST CHANGES** 🔄 The two required changes (extracting duplicated `_CODE_MAP` and documenting `-32009` in the spec) should be addressed before merge. The core implementation is sound. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
freemo reviewed 2026-04-05 17:05:27 +00:00
freemo left a comment
Author
Owner
Copy Link
Copy Source

🔍 Code Review — Architecture, Module Boundaries & Interface Contracts

Reviewed PR #3310 with focus on architecture-alignment, module-boundaries, and interface-contracts.

Overview

This PR correctly fixes a JSON-RPC 2.0 specification compliance defect: A2aErrorDetail.code was typed as str with string literal constants, but the JSON-RPC 2.0 specification (Section 5.1) mandates integer error codes. The fix changes the type to int and maps all error constants to their proper integer values from the docs/reference/a2a.md taxonomy.

The core implementation is sound. I'm adding architecture-focused observations that complement the previous review's test-quality findings.

Architecture Alignment

1. ✅ JSON-RPC 2.0 Wire Format Compliance — Correct

The integer code assignments align with the spec taxonomy in docs/reference/a2a.md:

Constant Code Spec Match
NOT_FOUND -32001 ✅
AUTH_ERROR -32002 ✅
FORBIDDEN -32003 ✅
INVALID_STATE -32004 ✅
PLAN_ERROR -32008 ✅
VALIDATION_ERROR -32602 ✅
INTERNAL_ERROR -32603 ✅
CONFIGURATION_ERROR -32009 ⚠️ Not in spec table

2. ⚠️ [SPEC GAP] CONFIGURATION_ERROR = -32009 — Not in docs/reference/a2a.md

  • Location: src/cleveragents/a2a/errors.py:44
  • Issue: The Error Code Taxonomy table in docs/reference/a2a.md ends at -32008 (PlanError). The code -32009 for ConfigurationError is not listed. The code's own comment block (lines 26-39) documents it, but the authoritative spec reference does not.
  • Per CONTRIBUTING.md: The specification is the source of truth. When there is a discrepancy between the codebase and the specification, the specification is considered correct.
  • Required: Update docs/reference/a2a.md Error Code Taxonomy table to include | -32009 | ConfigurationError | Configuration error |, or file a follow-up issue to track the spec update.

3. ⚠️ [SPEC GAP] Missing error code constants for spec-defined codes

The spec defines three additional error codes that have no corresponding constants in errors.py:

  • -32005 → DuplicateEntityError
  • -32006 → BudgetExceededError
  • -32007 → A2aVersionMismatchError

These are not blocking for this PR (which is scoped to fixing the str→int type), but they represent an incomplete mapping between the spec taxonomy and the code. Consider filing a follow-up issue.

Interface Contracts

4. ✅ map_domain_error() return type correctly updated

  • Before: tuple[str, str]
  • After: tuple[int, str]

This is a breaking change to the public API, but it's the correct fix. The function is exported in __all__ and its docstring is properly updated to document the new integer return type. All callers within the codebase are updated.

5. ✅ A2aErrorDetail.code type change — Correct Pydantic approach

  • Before: code: str with @field_validator("code", "message") checking non-empty
  • After: code: int with @field_validator("message") only

Removing code from the field validator is correct — Pydantic v2 enforces the int type annotation natively, so the non-empty string check is no longer applicable. The model_config = ConfigDict(strict=False) allows coercion from compatible types (e.g., float → int), which is appropriate for JSON deserialization.

6. ℹ️ [DOCSTRING] A2aErrorDetail docstring is slightly misleading

  • Location: src/cleveragents/a2a/models.py, A2aErrorDetail class docstring
  • Issue: The docstring states: "Application-defined codes must be outside this range" (referring to -32768 to -32000). However, the codes actually used (-32001 to -32009) ARE within this range — they are "implementation-defined server errors" per JSON-RPC 2.0, which is a valid use of this range. The docstring conflates "application-defined" with "implementation-defined server errors."
  • Suggestion (non-blocking): Clarify the docstring to distinguish between standard pre-defined codes (-32700 to -32600), implementation-defined server errors (-32099 to -32000), and application-defined codes (outside -32768 to -32000).

Module Boundaries

7. ⚠️ [DRY] _CODE_MAP duplicated across module boundaries

  • Locations: 6 definitions across 4 step files:

    • features/steps/a2a_facade_steps.py (×2: step_create_response, step_create_error_detail)
    • features/steps/a2a_facade_wiring_steps.py (×1: step_wired_error_code)
    • features/steps/a2a_facade_coverage_boost_steps.py (×1: step_cb_error_code)
    • features/steps/a2a_jsonrpc_wire_format_steps.py (×2: step_create_error_response, step_jsonrpc_error_response_dict)

  • Issue: This creates a coupling problem: the mapping between symbolic names and integer codes is now a de facto interface contract between the feature files and the step definitions, but it's defined 6 times with no single source of truth. If a code value changes or a new code is added, all 6 copies must be updated in lockstep.

  • Architectural recommendation: Extract to a shared test helper that derives the mapping programmatically from cleveragents.a2a.errors:

    # features/steps/_a2a_code_map.py
from cleveragents.a2a import errors as _err

A2A_CODE_MAP: dict[str, int] = {
    name: getattr(_err, name)
    for name in _err.__all__
    if isinstance(getattr(_err, name), int)
}

    This ensures the test mapping always stays in sync with the source module.

8. ✅ Robot Framework helpers correctly updated

Both robot/helper_a2a_facade_wiring.py and robot/helper_a2a_jsonrpc_wire_format.py are properly updated:

  • wired_error_mapping() now compares against integer codes from the errors module
  • response_error_wire_format() uses -32001 directly instead of "NOT_FOUND"

The Robot helpers import from cleveragents.a2a.errors directly rather than duplicating the mapping, which is the correct pattern.

CONTRIBUTING.md Compliance

Criterion Status
Conventional Changelog commit format ✅ fix(a2a): change A2aErrorDetail.code to int...
Single atomic commit ✅ One commit with all changes
ISSUES CLOSED: #2746 footer ✅ Present
PR has Closes #2746 ✅ Present in body
Milestone assigned (v3.8.0) ✅
Type/Bug label ✅
No # type: ignore introduced ✅ (pre-existing ones in wiring/wire-format steps not introduced by this PR)
File size limits ✅ All files under 500 lines

Pre-existing Issues (Not Introduced by This PR)

  • features/steps/a2a_facade_wiring_steps.py lines 20-22: # type: ignore[assignment,misc] in ImportError fallback
  • features/steps/a2a_jsonrpc_wire_format_steps.py lines 24-27: # type: ignore[assignment,misc] in ImportError fallback
  • features/steps/a2a_facade_coverage_boost_steps.py line 82: # type: ignore[arg-type] (intentional for testing TypeError path)

These violate CONTRIBUTING.md but are pre-existing. Consider a follow-up cleanup issue.

Summary

The core implementation is architecturally sound — it correctly aligns the A2A error code interface with JSON-RPC 2.0 requirements. The interface contract changes (str → int) are properly propagated through all layers (models, error constants, domain mapping, unit tests, integration tests).

Items requiring attention before merge:

  1. Spec gap for -32009 — Update docs/reference/a2a.md or file follow-up issue
  2. _CODE_MAP duplication — Extract to shared test helper to maintain module boundary hygiene

Non-blocking suggestions:
3. Clarify A2aErrorDetail docstring re: implementation-defined vs application-defined codes
4. Consider follow-up issue for missing spec codes (-32005, -32006, -32007)
5. Consider follow-up issue for pre-existing # type: ignore in test step files

Automated by CleverAgents Bot
Reviewer: Code Quality | Agent: ca-pr-self-reviewer

## 🔍 Code Review — Architecture, Module Boundaries & Interface Contracts Reviewed PR #3310 with focus on **architecture-alignment**, **module-boundaries**, and **interface-contracts**. ### Overview This PR correctly fixes a JSON-RPC 2.0 specification compliance defect: `A2aErrorDetail.code` was typed as `str` with string literal constants, but the JSON-RPC 2.0 specification (Section 5.1) mandates integer error codes. The fix changes the type to `int` and maps all error constants to their proper integer values from the `docs/reference/a2a.md` taxonomy. The core implementation is sound. I'm adding architecture-focused observations that complement the previous review's test-quality findings. --- ### Architecture Alignment #### 1. ✅ **JSON-RPC 2.0 Wire Format Compliance — Correct** The integer code assignments align with the spec taxonomy in `docs/reference/a2a.md`: | Constant | Code | Spec Match | |----------|------|------------| | `NOT_FOUND` | `-32001` | ✅ | | `AUTH_ERROR` | `-32002` | ✅ | | `FORBIDDEN` | `-32003` | ✅ | | `INVALID_STATE` | `-32004` | ✅ | | `PLAN_ERROR` | `-32008` | ✅ | | `VALIDATION_ERROR` | `-32602` | ✅ | | `INTERNAL_ERROR` | `-32603` | ✅ | | `CONFIGURATION_ERROR` | `-32009` | ⚠️ Not in spec table | #### 2. ⚠️ **[SPEC GAP] `CONFIGURATION_ERROR = -32009` — Not in `docs/reference/a2a.md`** - **Location:** `src/cleveragents/a2a/errors.py:44` - **Issue:** The Error Code Taxonomy table in `docs/reference/a2a.md` ends at `-32008` (PlanError). The code `-32009` for `ConfigurationError` is not listed. The code's own comment block (lines 26-39) documents it, but the authoritative spec reference does not. - **Per CONTRIBUTING.md:** The specification is the source of truth. When there is a discrepancy between the codebase and the specification, the specification is considered correct. - **Required:** Update `docs/reference/a2a.md` Error Code Taxonomy table to include `| -32009 | ConfigurationError | Configuration error |`, or file a follow-up issue to track the spec update. #### 3. ⚠️ **[SPEC GAP] Missing error code constants for spec-defined codes** The spec defines three additional error codes that have no corresponding constants in `errors.py`: - `-32005` → `DuplicateEntityError` - `-32006` → `BudgetExceededError` - `-32007` → `A2aVersionMismatchError` These are not blocking for this PR (which is scoped to fixing the str→int type), but they represent an incomplete mapping between the spec taxonomy and the code. Consider filing a follow-up issue. --- ### Interface Contracts #### 4. ✅ **`map_domain_error()` return type correctly updated** - **Before:** `tuple[str, str]` - **After:** `tuple[int, str]` This is a breaking change to the public API, but it's the correct fix. The function is exported in `__all__` and its docstring is properly updated to document the new integer return type. All callers within the codebase are updated. #### 5. ✅ **`A2aErrorDetail.code` type change — Correct Pydantic approach** - **Before:** `code: str` with `@field_validator("code", "message")` checking non-empty - **After:** `code: int` with `@field_validator("message")` only Removing `code` from the field validator is correct — Pydantic v2 enforces the `int` type annotation natively, so the non-empty string check is no longer applicable. The `model_config = ConfigDict(strict=False)` allows coercion from compatible types (e.g., `float` → `int`), which is appropriate for JSON deserialization. #### 6. ℹ️ **[DOCSTRING] `A2aErrorDetail` docstring is slightly misleading** - **Location:** `src/cleveragents/a2a/models.py`, `A2aErrorDetail` class docstring - **Issue:** The docstring states: *"Application-defined codes must be outside this range"* (referring to -32768 to -32000). However, the codes actually used (-32001 to -32009) ARE within this range — they are "implementation-defined server errors" per JSON-RPC 2.0, which is a valid use of this range. The docstring conflates "application-defined" with "implementation-defined server errors." - **Suggestion (non-blocking):** Clarify the docstring to distinguish between standard pre-defined codes (-32700 to -32600), implementation-defined server errors (-32099 to -32000), and application-defined codes (outside -32768 to -32000). --- ### Module Boundaries #### 7. ⚠️ **[DRY] `_CODE_MAP` duplicated across module boundaries** - **Locations:** 6 definitions across 4 step files: - `features/steps/a2a_facade_steps.py` (×2: `step_create_response`, `step_create_error_detail`) - `features/steps/a2a_facade_wiring_steps.py` (×1: `step_wired_error_code`) - `features/steps/a2a_facade_coverage_boost_steps.py` (×1: `step_cb_error_code`) - `features/steps/a2a_jsonrpc_wire_format_steps.py` (×2: `step_create_error_response`, `step_jsonrpc_error_response_dict`) - **Issue:** This creates a coupling problem: the mapping between symbolic names and integer codes is now a de facto interface contract between the feature files and the step definitions, but it's defined 6 times with no single source of truth. If a code value changes or a new code is added, all 6 copies must be updated in lockstep. - **Architectural recommendation:** Extract to a shared test helper that derives the mapping programmatically from `cleveragents.a2a.errors`: ```python # features/steps/_a2a_code_map.py from cleveragents.a2a import errors as _err A2A_CODE_MAP: dict[str, int] = { name: getattr(_err, name) for name in _err.__all__ if isinstance(getattr(_err, name), int) } ``` This ensures the test mapping always stays in sync with the source module. #### 8. ✅ **Robot Framework helpers correctly updated** Both `robot/helper_a2a_facade_wiring.py` and `robot/helper_a2a_jsonrpc_wire_format.py` are properly updated: - `wired_error_mapping()` now compares against integer codes from the errors module - `response_error_wire_format()` uses `-32001` directly instead of `"NOT_FOUND"` The Robot helpers import from `cleveragents.a2a.errors` directly rather than duplicating the mapping, which is the correct pattern. --- ### CONTRIBUTING.md Compliance | Criterion | Status | |-----------|--------| | Conventional Changelog commit format | ✅ `fix(a2a): change A2aErrorDetail.code to int...` | | Single atomic commit | ✅ One commit with all changes | | `ISSUES CLOSED: #2746` footer | ✅ Present | | PR has `Closes #2746` | ✅ Present in body | | Milestone assigned (v3.8.0) | ✅ | | `Type/Bug` label | ✅ | | No `# type: ignore` introduced | ✅ (pre-existing ones in wiring/wire-format steps not introduced by this PR) | | File size limits | ✅ All files under 500 lines | --- ### Pre-existing Issues (Not Introduced by This PR) - `features/steps/a2a_facade_wiring_steps.py` lines 20-22: `# type: ignore[assignment,misc]` in ImportError fallback - `features/steps/a2a_jsonrpc_wire_format_steps.py` lines 24-27: `# type: ignore[assignment,misc]` in ImportError fallback - `features/steps/a2a_facade_coverage_boost_steps.py` line 82: `# type: ignore[arg-type]` (intentional for testing TypeError path) These violate CONTRIBUTING.md but are pre-existing. Consider a follow-up cleanup issue. --- ### Summary The core implementation is **architecturally sound** — it correctly aligns the A2A error code interface with JSON-RPC 2.0 requirements. The interface contract changes (`str` → `int`) are properly propagated through all layers (models, error constants, domain mapping, unit tests, integration tests). **Items requiring attention before merge:** 1. **Spec gap for `-32009`** — Update `docs/reference/a2a.md` or file follow-up issue 2. **`_CODE_MAP` duplication** — Extract to shared test helper to maintain module boundary hygiene **Non-blocking suggestions:** 3. Clarify `A2aErrorDetail` docstring re: implementation-defined vs application-defined codes 4. Consider follow-up issue for missing spec codes (-32005, -32006, -32007) 5. Consider follow-up issue for pre-existing `# type: ignore` in test step files --- **Automated by CleverAgents Bot** Reviewer: Code Quality | Agent: ca-pr-self-reviewer
freemo force-pushed fix/a2a-error-codes-integer-jsonrpc2 from 538158526c to f5d244cd37 2026-04-05 17:54:02 +00:00 Compare
freemo commented 2026-04-05 17:54:18 +00:00
Author
Owner
Copy Link
Copy Source

Review Feedback Addressed

Both required changes from the REQUEST CHANGES review have been implemented and pushed (amended commit f5d244cd).

Required Change 1: _CODE_MAP duplication → shared module ✅

Extracted to features/steps/_a2a_code_map.py — a new shared module that derives the mapping directly from cleveragents.a2a.errors constants:

# features/steps/_a2a_code_map.py
from cleveragents.a2a import errors as _a2a_errors

A2A_CODE_MAP: dict[str, int] = {
    "NOT_FOUND": _a2a_errors.NOT_FOUND,
    "AUTH_ERROR": _a2a_errors.AUTH_ERROR,
    ...
}

All 4 step files now import A2A_CODE_MAP from this single source of truth:

  • features/steps/a2a_facade_steps.py — 2 inline _CODE_MAP dicts removed
  • features/steps/a2a_facade_wiring_steps.py — 1 inline _CODE_MAP dict removed
  • features/steps/a2a_facade_coverage_boost_steps.py — 1 inline _CODE_MAP dict removed
  • features/steps/a2a_jsonrpc_wire_format_steps.py — 2 inline _CODE_MAP dicts removed

Total: 6 duplicate definitions → 1 canonical definition.

Required Change 2: CONFIGURATION_ERROR = -32009 documented in spec ✅

Added to the Error Code Taxonomy table in docs/reference/a2a.md:

| `-32009`          | `ConfigurationError`                   | Configuration error              |

The table now covers all 8 error constants defined in errors.py.

All files pass Ruff linting with zero violations.

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

## Review Feedback Addressed Both required changes from the REQUEST CHANGES review have been implemented and pushed (amended commit `f5d244cd`). ### Required Change 1: `_CODE_MAP` duplication → shared module ✅ **Extracted to `features/steps/_a2a_code_map.py`** — a new shared module that derives the mapping directly from `cleveragents.a2a.errors` constants: ```python # features/steps/_a2a_code_map.py from cleveragents.a2a import errors as _a2a_errors A2A_CODE_MAP: dict[str, int] = { "NOT_FOUND": _a2a_errors.NOT_FOUND, "AUTH_ERROR": _a2a_errors.AUTH_ERROR, ... } ``` All 4 step files now import `A2A_CODE_MAP` from this single source of truth: - `features/steps/a2a_facade_steps.py` — 2 inline `_CODE_MAP` dicts removed - `features/steps/a2a_facade_wiring_steps.py` — 1 inline `_CODE_MAP` dict removed - `features/steps/a2a_facade_coverage_boost_steps.py` — 1 inline `_CODE_MAP` dict removed - `features/steps/a2a_jsonrpc_wire_format_steps.py` — 2 inline `_CODE_MAP` dicts removed Total: 6 duplicate definitions → 1 canonical definition. ### Required Change 2: `CONFIGURATION_ERROR = -32009` documented in spec ✅ Added to the Error Code Taxonomy table in `docs/reference/a2a.md`: ``` | `-32009` | `ConfigurationError` | Configuration error | ``` The table now covers all 8 error constants defined in `errors.py`. --- All files pass Ruff linting with zero violations. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
freemo reviewed 2026-04-05 19:40:20 +00:00
freemo left a comment
Author
Owner
Copy Link
Copy Source

🔍 Code Review — APPROVED ✅

Reviewed PR #3310 with focus on api-consistency, naming-conventions, and code-patterns.

This PR fixes a JSON-RPC 2.0 specification compliance defect where A2aErrorDetail.code was typed as str with string literal constants, but the JSON-RPC 2.0 specification (Section 5.1) mandates integer error codes. The fix correctly changes the type to int and maps all error constants to their proper integer values per the docs/reference/a2a.md taxonomy.

I note that a previous review (now stale) requested two changes — extracting duplicated _CODE_MAP to a shared module and documenting -32009 in the spec — and both have been addressed in the amended commit.

Deep Dive: API Consistency ✅

  • A2aErrorDetail.code: int — Correctly matches JSON-RPC 2.0 Section 5.1 requirement. The model_config = ConfigDict(strict=False) appropriately allows coercion from compatible types during JSON deserialization.
  • map_domain_error() return type — Properly updated from tuple[str, str] to tuple[int, str]. The docstring is updated to document the new integer return type. All callers are updated consistently.
  • __all__ exports — Both errors.py and models.py have complete __all__ lists covering all public symbols. The 8 error code constants, 4 exception classes, and map_domain_error are all exported.
  • Error code taxonomy alignment — All 8 constants match the docs/reference/a2a.md Error Code Taxonomy table (which now includes -32009 for ConfigurationError).
  • Pydantic field_validator — Correctly narrowed from ("code", "message") to ("message") only, since Pydantic v2 enforces the int type annotation natively. The non-empty string check is no longer applicable to an integer field.

Deep Dive: Naming Conventions ✅

  • Error code constants — All use UPPER_SNAKE_CASE consistently: NOT_FOUND, AUTH_ERROR, FORBIDDEN, INVALID_STATE, PLAN_ERROR, CONFIGURATION_ERROR, VALIDATION_ERROR, INTERNAL_ERROR.
  • Exception classes — All use PascalCase with A2a prefix: A2aError, A2aNotAvailableError, A2aVersionMismatchError, A2aOperationNotFoundError. Consistent with project conventions.
  • Shared test helper — _a2a_code_map.py uses underscore prefix appropriately for an internal module. The constant A2A_CODE_MAP uses UPPER_SNAKE_CASE correctly for a module-level constant.
  • Type annotations — All constants have explicit type annotations (int), all function signatures are fully typed, and return types are specified.

Deep Dive: Code Patterns ✅

  • Single source of truth for code mapping — features/steps/_a2a_code_map.py derives values directly from cleveragents.a2a.errors constants rather than hardcoding integers. This ensures the test mapping stays in sync with the source module automatically. Excellent pattern.
  • Symbolic name resolution in step definitions — The pattern A2A_CODE_MAP.get(code, int(code) if code.lstrip("-").isdigit() else _a2a_errors.INTERNAL_ERROR) handles both symbolic names from Gherkin and raw integer strings gracefully. Consistent across all step files.
  • map_domain_error() precedence chain — The isinstance chain correctly checks specific exception types before their base classes (e.g., PlanError before BusinessRuleViolation, CleverAgentsError as final catch-all). This prevents incorrect classification.
  • Backward-compatible Gherkin — Feature files continue to use human-readable symbolic names ("NOT_FOUND") while step definitions handle the mapping. This preserves test readability without coupling feature files to implementation details.

Standard Criteria

Criterion Status
Conventional Changelog commit format ✅ fix(a2a): change A2aErrorDetail.code to int...
Single atomic commit ✅ One commit with all changes
ISSUES CLOSED: #2746 footer ✅ Present
PR has Closes #2746 ✅ Present in body
Milestone assigned (v3.8.0) ✅
Type/Bug label ✅
No new # type: ignore introduced ✅
File size limits ✅ All files under 500 lines
Spec alignment ✅ docs/reference/a2a.md updated with -32009

Minor Suggestions (Non-blocking)

  1. Duplicate A2aResponse construction in features/steps/a2a_jsonrpc_wire_format_steps.py — In step_create_error_response(), context.response is assigned twice with identical values:

    context.response = A2aResponse(
    id=resp_id,
    error=A2aErrorDetail(code=int_code, message="Resource not found"),
)
context.response = A2aResponse(
    id=resp_id,
    error=A2aErrorDetail(code=int_code, message="Resource not found"),
)

    The second assignment overwrites the first with the same value. This is harmless but appears to be a copy-paste artifact. Consider removing the duplicate.

  2. A2aErrorDetail docstring precision — The docstring states "Application-defined codes must be outside this range" (referring to -32768 to -32000), but the codes used (-32001 to -32009) are within this range as "implementation-defined server errors" per JSON-RPC 2.0. This is technically correct usage but the docstring wording could be more precise. Non-blocking.

  3. Missing error code constants for spec-defined codes — The spec defines -32005 (DuplicateEntityError), -32006 (BudgetExceededError), and -32007 (A2aVersionMismatchError) but these don't have corresponding constants in errors.py. This is a pre-existing gap outside the scope of this PR, but worth a follow-up issue.

  4. Pre-existing # type: ignore in test files — a2a_facade_wiring_steps.py and a2a_jsonrpc_wire_format_steps.py contain # type: ignore[assignment,misc] in their ImportError fallback blocks. These are pre-existing (not introduced by this PR) but violate CONTRIBUTING.md. Worth a follow-up cleanup.

Decision: APPROVED ✅

The implementation is correct, the API changes are consistent, naming follows project conventions, and code patterns are clean. The previous review's required changes have been properly addressed. The core str → int type change is well-propagated through all layers (models, error constants, domain mapping, unit tests, integration tests, spec documentation).

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

## 🔍 Code Review — APPROVED ✅ Reviewed PR #3310 with focus on **api-consistency**, **naming-conventions**, and **code-patterns**. This PR fixes a JSON-RPC 2.0 specification compliance defect where `A2aErrorDetail.code` was typed as `str` with string literal constants, but the JSON-RPC 2.0 specification (Section 5.1) mandates integer error codes. The fix correctly changes the type to `int` and maps all error constants to their proper integer values per the `docs/reference/a2a.md` taxonomy. I note that a previous review (now stale) requested two changes — extracting duplicated `_CODE_MAP` to a shared module and documenting `-32009` in the spec — and both have been addressed in the amended commit. --- ### Deep Dive: API Consistency ✅ - **`A2aErrorDetail.code: int`** — Correctly matches JSON-RPC 2.0 Section 5.1 requirement. The `model_config = ConfigDict(strict=False)` appropriately allows coercion from compatible types during JSON deserialization. - **`map_domain_error()` return type** — Properly updated from `tuple[str, str]` to `tuple[int, str]`. The docstring is updated to document the new integer return type. All callers are updated consistently. - **`__all__` exports** — Both `errors.py` and `models.py` have complete `__all__` lists covering all public symbols. The 8 error code constants, 4 exception classes, and `map_domain_error` are all exported. - **Error code taxonomy alignment** — All 8 constants match the `docs/reference/a2a.md` Error Code Taxonomy table (which now includes `-32009` for `ConfigurationError`). - **Pydantic field_validator** — Correctly narrowed from `("code", "message")` to `("message")` only, since Pydantic v2 enforces the `int` type annotation natively. The non-empty string check is no longer applicable to an integer field. ### Deep Dive: Naming Conventions ✅ - **Error code constants** — All use `UPPER_SNAKE_CASE` consistently: `NOT_FOUND`, `AUTH_ERROR`, `FORBIDDEN`, `INVALID_STATE`, `PLAN_ERROR`, `CONFIGURATION_ERROR`, `VALIDATION_ERROR`, `INTERNAL_ERROR`. - **Exception classes** — All use `PascalCase` with `A2a` prefix: `A2aError`, `A2aNotAvailableError`, `A2aVersionMismatchError`, `A2aOperationNotFoundError`. Consistent with project conventions. - **Shared test helper** — `_a2a_code_map.py` uses underscore prefix appropriately for an internal module. The constant `A2A_CODE_MAP` uses `UPPER_SNAKE_CASE` correctly for a module-level constant. - **Type annotations** — All constants have explicit type annotations (`int`), all function signatures are fully typed, and return types are specified. ### Deep Dive: Code Patterns ✅ - **Single source of truth for code mapping** — `features/steps/_a2a_code_map.py` derives values directly from `cleveragents.a2a.errors` constants rather than hardcoding integers. This ensures the test mapping stays in sync with the source module automatically. Excellent pattern. - **Symbolic name resolution in step definitions** — The pattern `A2A_CODE_MAP.get(code, int(code) if code.lstrip("-").isdigit() else _a2a_errors.INTERNAL_ERROR)` handles both symbolic names from Gherkin and raw integer strings gracefully. Consistent across all step files. - **`map_domain_error()` precedence chain** — The isinstance chain correctly checks specific exception types before their base classes (e.g., `PlanError` before `BusinessRuleViolation`, `CleverAgentsError` as final catch-all). This prevents incorrect classification. - **Backward-compatible Gherkin** — Feature files continue to use human-readable symbolic names (`"NOT_FOUND"`) while step definitions handle the mapping. This preserves test readability without coupling feature files to implementation details. ### Standard Criteria | Criterion | Status | |-----------|--------| | Conventional Changelog commit format | ✅ `fix(a2a): change A2aErrorDetail.code to int...` | | Single atomic commit | ✅ One commit with all changes | | `ISSUES CLOSED: #2746` footer | ✅ Present | | PR has `Closes #2746` | ✅ Present in body | | Milestone assigned (v3.8.0) | ✅ | | `Type/Bug` label | ✅ | | No new `# type: ignore` introduced | ✅ | | File size limits | ✅ All files under 500 lines | | Spec alignment | ✅ `docs/reference/a2a.md` updated with `-32009` | ### Minor Suggestions (Non-blocking) 1. **Duplicate `A2aResponse` construction in `features/steps/a2a_jsonrpc_wire_format_steps.py`** — In `step_create_error_response()`, `context.response` is assigned twice with identical values: ```python context.response = A2aResponse( id=resp_id, error=A2aErrorDetail(code=int_code, message="Resource not found"), ) context.response = A2aResponse( id=resp_id, error=A2aErrorDetail(code=int_code, message="Resource not found"), ) ``` The second assignment overwrites the first with the same value. This is harmless but appears to be a copy-paste artifact. Consider removing the duplicate. 2. **`A2aErrorDetail` docstring precision** — The docstring states *"Application-defined codes must be outside this range"* (referring to -32768 to -32000), but the codes used (-32001 to -32009) are within this range as "implementation-defined server errors" per JSON-RPC 2.0. This is technically correct usage but the docstring wording could be more precise. Non-blocking. 3. **Missing error code constants for spec-defined codes** — The spec defines `-32005` (DuplicateEntityError), `-32006` (BudgetExceededError), and `-32007` (A2aVersionMismatchError) but these don't have corresponding constants in `errors.py`. This is a pre-existing gap outside the scope of this PR, but worth a follow-up issue. 4. **Pre-existing `# type: ignore` in test files** — `a2a_facade_wiring_steps.py` and `a2a_jsonrpc_wire_format_steps.py` contain `# type: ignore[assignment,misc]` in their `ImportError` fallback blocks. These are pre-existing (not introduced by this PR) but violate CONTRIBUTING.md. Worth a follow-up cleanup. **Decision: APPROVED** ✅ The implementation is correct, the API changes are consistent, naming follows project conventions, and code patterns are clean. The previous review's required changes have been properly addressed. The core `str` → `int` type change is well-propagated through all layers (models, error constants, domain mapping, unit tests, integration tests, spec documentation). --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
freemo merged commit ef557a31a9 into master 2026-04-05 21:10:15 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
freemo
Labels
Clear labels
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
 controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
 overdue
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Milestone
No items
No Milestone v3.8.0
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#2746 UAT: A2aErrorDetail.code is str but JSON-RPC 2.0 requires integer error codes; map_domain_error returns string codes instead of integer codes
cleveragents/cleveragents-core
Reference: cleveragents/cleveragents-core#3310
Delete Branch "fix/a2a-error-codes-integer-jsonrpc2"

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?