docs(spec): What changed from v0.3.0 to v1.0

[darrelmiller]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @darrelmiller, 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!

The v1.0 release of the A2A Protocol marks a significant maturation, focusing on standardization, enhanced type safety, improved developer experience, and enterprise-ready features. It introduces formal adherence to industry specifications, refines core data models and operations, and clarifies behavioral semantics, necessitating updates for existing implementations while providing a more robust and consistent foundation for future development.

Highlights

• Part Type Unification: The Part object has been completely redesigned, unifying TextPart, FilePart, and DataPart into a single structure and removing the kind discriminator in favor of member-based polymorphism.
• Enum Value Standardization: All enum values (e.g., TaskStatus.state, Message.role) have been changed from PascalCase or lowercase to SCREAMING_SNAKE_CASE with type prefixes (e.g., "completed" to "TASK_STATE_COMPLETED").
• Agent Card Restructuring: The AgentCard object has undergone significant changes, including the consolidation of interface details into supportedInterfaces[], the addition of agentId and signatures[] for verification, and the relocation of supportsAuthenticatedExtendedCard to capabilities.extendedAgentCard.
• Stream Event Discrimination: Stream events (TaskStatusUpdateEvent, TaskArtifactUpdateEvent) no longer use a kind discriminator; instead, their type is determined by a wrapper-based JSON member name (e.g., taskStatusUpdate or taskArtifactUpdate).
• Cursor-Based Pagination: The ListTasks operation now uses cursor-based pagination for improved scalability, replacing the previous page-number-based approach.
• New Specifications Adoption: The protocol now formally depends on several industry standards, including RFC 9457 for error details, RFC 8785 for JSON Canonicalization, RFC 7515 for JWS (for Agent Card signatures), and ISO 8601 for timestamp formatting.

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive "What's New" document for the A2A Protocol v1.0, which is a great addition for developers migrating from v0.3.0. The document is well-structured and covers the major changes in detail. I've identified a few areas with inconsistencies or inaccuracies that could be improved for clarity. My review includes suggestions to correct a code example, remove a misleading section, and fix minor inconsistencies in terminology and descriptions. Overall, this is a valuable piece of documentation.

[muscariello]

LGTM

[darrelmiller]

@holtskinner Thank you for the review and suggestions. I have applied your changes.

[holtskinner]

@gemini-code-assist review

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive and well-structured document, docs/whats-new-v1.md, which details the changes from A2A Protocol v0.3.0 to v1.0. The document is thorough, covering major themes, breaking changes, and providing a migration guide for developers. The changes are clearly explained with helpful code examples. I've included a few minor suggestions to improve consistency and clarity in the document. Overall, this is an excellent addition to the project's documentation.