StreamTextResult

Streaming generation result — memoised replay. A terminal upstream run is collected at most once; later collectors replay the captured events. If every collector leaves before the upstream reaches a terminal state, that producer is cancelled, its partial buffer is discarded, and a later collector starts a fresh upstream run. To preserve full replay for a collector that attaches after the first event, the result keeps the terminal stream event sequence in memory for the result lifetime. Hosts that need minimum peak memory for a guaranteed single-consumer path can collect the model stream directly instead of using this replaying result surface.

Streaming has no default deadline. High-level callers should set CallConfig.timeout, and low-level callers should configure the underlying HTTP/on-device engine socket timeout, so a dead SSE or local engine stream cannot wait forever.