Transcript components now share one turn object, and remote sessions write into the same transcript store.
What's wrong with this entry?
Transcript components that each received separate streaming, loading and auto-queue callbacks now take a single turn object, with a shared helper deciding whether a response is still streaming. Remote sessions push into the same transcript store rather than setting messages and loading state directly.
- The helper prefers an optional
getIsResponseStreaming()callback and falls back to the turn's mid-turn flag when it is absent. - Remote-session hooks now call
setExternalLoadingandmarkRemoteTurnCompleteinstead of the old message and loading setters.
getIsResponseStreaming
Strings lifted out of the shipped bundle, so the claim above can be checked against them.