From a host to a checked call
Three stages, top to bottom, drawn step by step. First, the planner finds the code-reviewer card: direct configuration gives it the host, and a GET of /.well-known/agent-card.json returns the card, while a registry is a third route the kit does not use. Second, the planner takes interface 0, JSON-RPC 1.0 at /a2a/jsonrpc, and skips interface 1, HTTP+JSON. Third, it reads the capability flags: streaming is true and pushNotifications is absent, and a CreateTaskPushNotificationConfig call that ignores the absent flag fails with error -32003.
1 · FIND THE CARD
2 · TAKE THE FIRST INTERFACE YOU SPEAK
3 · CHECK THE FLAG BEFORE AN OPTIONAL CALL
direct configuration
ports 41241, 41242, 41243
well-known URI
GET /.well-known/
agent-card.json
GET
code-reviewer
agent card
200 OK
registry or catalog
no standard query API
or a registry query
[0] JSONRPC, "1.0", http://localhost:41242/a2a/jsonrpc
chosen
[1] HTTP+JSON, "1.0", http://localhost:41242/a2a/rest
skipped: not JSON-RPC
streaming: true
SendStreamingMessage, SubscribeToTask
pushNotifications: absent
the four push config operations fail
exchange 6 of 11-errors.http calls one anyway:
planner
client
code-reviewer
/a2a/jsonrpc
CreateTaskPushNotificationConfig
-32003 PUSH_NOTIFICATION_NOT_SUPPORTED