AS_STREAMED

Emit the same chunks the provider produced, one after another, with no delay. The default.

The content is identical to what the original caller received, boundary for boundary: a collector that concatenates gets the same string, and a collector that renders per chunk renders the same steps. Only the wait is gone, which is the part the cache was hired to remove.

An entry written by any path other than SemanticCache.getOrPutStreaming has no recorded boundaries, so it replays as a single chunk. That is not a special case, it is the truth about that entry: nobody ever streamed it.