One streamed task from the card read to the close
Two lifelines, planner and test-runner at localhost:41241. The planner reads the agent card, sends SendStreamingMessage with a new messageId and no taskId, and gets HTTP 200 with text/event-stream. Nine numbered stream frames follow: the task 728ba084 in TASK_STATE_SUBMITTED, a statusUpdate to TASK_STATE_WORKING, five artifactUpdate frames that build test-log.txt, the last with lastChunk, one artifactUpdate for summary.json, and a statusUpdate to TASK_STATE_COMPLETED. Only frames 1, 2 and 9 carry a timestamp, at 09:00:01.750Z, 09:00:02.000Z and 09:00:02.250Z. Then the server closes the stream, with no final flag.
planner
client agent
test-runner
localhost:41241
KIT CLOCK
GET /.well-known/agent-card.json
AgentCard, capabilities.streaming: true
SendStreamingMessage
messageId 5bc8fbbc, no taskId
HTTP 200, text/event-stream
1
task · TASK_STATE_SUBMITTED
task 728ba084, history holds the request
09:00:01.750Z
2
statusUpdate · TASK_STATE_WORKING
Checking out 9f3c2e1 and starting the suite
09:00:02.000Z
3
artifactUpdate · test-log.txt
first chunk: collected 12 items
4
artifactUpdate · append
5
artifactUpdate · append
6
artifactUpdate · append
7
artifactUpdate · append, lastChunk
8
artifactUpdate · summary.json, lastChunk
9
statusUpdate · TASK_STATE_COMPLETED
1 failed, 11 passed
09:00:02.250Z
frames 3 to 8
carry no
timestamp
the server closes the stream after frame 9, with no final flag