fix: trim comments

[JakubWorek]

Description

Summary

Trimmed boilerplate comments across files

Fixes #490

[github-actions]

🧪 Code Coverage

⬇️ Download Full Report

	Base	PR	Delta
src/compat/v0_3/server/express/rest_handler.ts	72.04%	71.94%	🔴 -0.10%
src/compat/v0_3/translate/security.ts	98.32%	98.73%	🟢 +0.41%
Total	90.72%	90.73%	🟢 +0.01%

Generated by coverage-comment.yml

[gemini-code-assist]

Code Review

This pull request refactors the A2A SDK by streamlining documentation, simplifying code comments, and updating Genkit dependencies in the samples. It also adjusts version parsing to default empty or nullish inputs to the legacy '0.3' version. Key feedback suggests trimming version strings in isLegacyVersion to robustly handle whitespace-only inputs, and explicitly handling Date objects in the cleanEmpty utility of src/signature.ts to prevent them from being serialized as empty objects.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[bartek-gralewicz]

I suggest to split this PR into separate ones. The repo-wide doc/comment update should not include logic changes, such should be a separate PR.

I propose to keep this PR as doc-related and move logic changes to ->

• Fixes as described in the PR description (if related, for unrelated it is recommended to do PR per fix)
• Updates (version changes, etc)
• Samples I would leave up to your judgement, whether these are under "fixes" scope or should have a separate PR as well.