Server-sent event stream of inbound activity

For an application that wants to react to replies in its own process. It requires holding the connection open — if you would rather not, attach a flow and let Cadence answer, then read GET /v1/conversations/{id}/answers.

Events: ready on connect, ping every 15s, then reply, fellback, help, optout and completed. Scoped to conversations this key or account owns — agentId is a convenience filter, not a boundary.