What happened?

In the table here https://a2a-protocol.org/latest/specification/#356-method-mapping-reference-table the same method is called:

tasks/resubscribe in JSON-RPC
TaskSubscription in gRPC
/v1/tasks/{id}:subscribe in HTTP

There are two reasonable outcomes here:

1. We rename the gRPC TaskSubscription to TaskResubscription and the HTTP URL to /v1/tasks/{id}:resubscribe

2. The JSON RPC method is changed to tasks/subscribe and we update the behaviour of the method to allow subscribing to a task even if it was started using message/send.

Thoughts?

Relevant log output

Code of Conduct

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