Opening a completed team conversation can display its final answer twice even though its transcript contains one assistant message. Reproduced during an ordinary invoice-tool workflow on 9a2c7cdd5: the checker ran the tool and reported once, but selecting its tab showed the same 536-character answer twice.
The two display inputs overlap: atomic AttachReplay returns the completed answer, while the hosted connection still offers the canonical turn through Follow. They have different channel identities, so channel-based checks do not recognize the replayed turn. A fix must preserve new replies (including identical text), in-flight observer output, and engine-restart ownership.
The original recording and single-message transcript are preserved. This is distinct from #1637, which concerns stream identifiers reused after an engine restart and a missing next reply. No fix or final verification is claimed yet.
Opening a completed team conversation can display its final answer twice even though its transcript contains one assistant message. Reproduced during an ordinary invoice-tool workflow on
9a2c7cdd5: the checker ran the tool and reported once, but selecting its tab showed the same 536-character answer twice.The two display inputs overlap: atomic
AttachReplayreturns the completed answer, while the hosted connection still offers the canonical turn throughFollow. They have different channel identities, so channel-based checks do not recognize the replayed turn. A fix must preserve new replies (including identical text), in-flight observer output, and engine-restart ownership.The original recording and single-message transcript are preserved. This is distinct from #1637, which concerns stream identifiers reused after an engine restart and a missing next reply. No fix or final verification is claimed yet.