[Bug]: Check that we have a test that uses pushNotificationConfig for MessageSendConfiguration

[fjuma]

What happened?

The A2A Java SDK had an issue where we were using pushNotification instead of pushNotificationConfig for MessageSendConfiguration:

a2aproject/a2a-java#286

The strange thing is that we didn't see a TCK failure related to this. The TCK server agent we are using does support push notifications.

It might be that the TCK was correctly sending pushNotificationConfig but A2A Java was just ignoring it since it considered this to be an unknown option and isn't required.

We should check to see that there's a test that uses pushNotificationConfig successfully. However, the TCK server agent would probably need to actually send a push notification about a task update using the provided pushNotificationConfig in order to verify that it's used properly.

Code of Conduct

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

[fjuma]

When sending a message with pushNotificationConfig specified, the pushNotificationConfig will be saved to the push notification config store. So the TCK could probably then try to get the push notification config or list the push notification config and it should find what was specified when sending the message. This could be a way to validate the specified value actually got used successfully.