[Bug]: A2A proto still uses compound identifiers for some messages #1390

What happened?

Some operations like GetTask / SubscribeToTask still used complex / compound identifiers like tasks/<uuid> or tasks/<uuid>/pushNotificationConfigs which requires the clients/servers to deconstruct/construct these IDs as they are normally using just the UUID to store the resource in the DB etc.

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct