fix(a2a): rename A2aErrorDetail.details to data per JSON-RPC 2.0 spec #3281

Merged
freemo merged 1 commits from fix/a2a-error-detail-data-field into master 2026-04-05 21:08:46 +00:00

1 Commits

Author SHA1 Message Date
freemo c1ebacd1b9 fix(a2a): rename A2aErrorDetail.details to data per JSON-RPC 2.0 spec
CI / lint (pull_request) Successful in 27s
CI / typecheck (pull_request) Successful in 51s
CI / quality (pull_request) Successful in 30s
CI / security (pull_request) Successful in 1m3s
CI / build (pull_request) Successful in 17s
CI / helm (pull_request) Successful in 28s
CI / unit_tests (pull_request) Successful in 6m57s
CI / e2e_tests (pull_request) Successful in 18m7s
CI / integration_tests (pull_request) Successful in 22m32s
CI / docker (pull_request) Successful in 1m20s
CI / coverage (pull_request) Successful in 10m56s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 58m46s
The A2aErrorDetail model used a field named 'details' for the optional
error payload, but JSON-RPC 2.0 §5.1 and the project specification both
require this field to be named 'data'.

Changes:
- Rename A2aErrorDetail.details -> data in src/cleveragents/a2a/models.py
- Add TDD BDD scenarios to features/a2a_jsonrpc_wire_format.feature that
  verify A2aErrorDetail serializes with 'data' field (not 'details')
- Add corresponding step definitions in a2a_jsonrpc_wire_format_steps.py

No call sites used the 'details' keyword argument when constructing
A2aErrorDetail instances (all existing usages only set code and message),
so no other files required changes.

ISSUES CLOSED: #2745
2026-04-05 08:57:12 +00:00