fix: expose HTTP status code in JSONRPCTransport errors

[pratik3558]

Previously, when the JSONRPC transport received a non-2xx HTTP response, it threw a plain IOException with the status code embedded as a string (e.g. "Request failed 503"). This made it impossible for callers to programmatically distinguish 4xx from 5xx errors without fragile string parsing.

This change makes the structured HTTP status code available while remaining fully backward compatible:

• JSONRPCTransport.sendPostRequest now throws A2AClientException with an A2AClientHTTPError as the cause, instead of a plain IOException. All transport methods already declared 'throws A2AClientException' and already had 'catch (A2AClientException e) { throw e; }', so no caller signatures change.

• A2AClientHTTPError gains a new 'responseBody' field (and getResponseBody() accessor) so callers can also inspect the raw error payload returned by the server (e.g. a gateway's JSON error body on a 429 or 503). The existing 'code', 'message', and getCode() are preserved unchanged. The old Object-typed constructor is deprecated in favour of the new String-typed one that actually stores the body.

Callers that want the status code can now opt in with a simple instanceof check, while existing catch blocks for A2AClientException continue to work without modification:

} catch (A2AClientException e) {
    if (e.getCause() instanceof A2AClientHTTPError httpErr) {
        int status = httpErr.getCode();          // e.g. 503
        String body = httpErr.getResponseBody(); // raw response body
    }
}

Description

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Follow the CONTRIBUTING Guide.
• Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
  • Important Prefixes for release-please:
    • fix: which represents bug fixes, and correlates to a SemVer patch.
    • feat: represents a new feature, and correlates to a SemVer minor.
    • feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.
• Ensure the tests pass
• Appropriate READMEs were updated (if necessary)

Fixes #799 🦕

[gemini-code-assist]

Code Review

This pull request enhances HTTP error handling by introducing A2AClientHTTPError as a structured cause within A2AClientException, allowing callers to retrieve the HTTP status code and response body. Feedback highlights a missing throws declaration for A2AClientException in the sendPostRequest method, which would lead to a compilation error, and suggests refactoring duplicated error message strings for better maintainability.

[pratik3558]

@kabir Could you review this code as well when you get a chance, please? Thank you

[pratik3558]

@kabir Could you please check?

[kabir]

Hi @ehsavoie I think you had some input on this one?

[ehsavoie]

I'd rather have an empty string instead of null. That way we could drop the @nullable on the responseBodyy