fix: export transport agnostic errors from client

[ishymko]

Description

Due to a name conflict with legacy JSON-RPC types reexported from src/index.ts below errors are going to be exported via src/client/index.ts to allow usage from external transport implementations.

[gemini-code-assist]

Summary of Changes

Hello @ishymko, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a naming conflict by relocating the export of several transport-agnostic error types. These errors, previously intended for re-export from src/index.ts, are now explicitly exported through src/client/index.ts. This change ensures that external transport implementations can correctly access and utilize these error types without encountering conflicts with legacy JSON-RPC definitions, improving overall system robustness and clarity.

Highlights

• Error Export Relocation: Transport-agnostic error types, such as TaskNotFoundError and UnsupportedOperationError, are now explicitly exported from src/client/index.ts.
• Name Conflict Resolution: This change addresses a name conflict with legacy JSON-RPC types that were previously re-exported from src/index.ts.
• Improved External Transport Compatibility: The new export path allows external transport implementations to correctly utilize these error types without encountering conflicts.
• Documentation Update: Comments within src/errors.ts have been updated to provide a clearer explanation of the rationale behind this export strategy and reference the A2A protocol specification.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

🧪 Code Coverage

⬇️ Download Full Report

Metric	Main	PR	Delta
lines	82.33%	82.31%	🔴 -0.02%
statements	82.33%	82.31%	🔴 -0.02%
functions	89.81%	89.81%	⚪️ 0.00%
branches	82.9%	82.9%	⚪️ 0.00%

Generated by coverage-comment.yml

[gemini-code-assist]

Code Review

This pull request refactors error exports to resolve a naming conflict, which is a good improvement. My review includes a few suggestions to enhance code style and documentation clarity. Specifically, I recommend sorting the new exports in src/client/index.ts for better readability and adjusting the comments in src/errors.ts to ensure both the error codes and classes have clear, distinct documentation.