docs(chat): note that a recovered answer needs a refresh to appear

The recovered answer is persisted correctly, but a chat page open across
the crash keeps showing the partial it already received. Say so in the
changeset rather than letting the release note imply the recovery is
visible without reloading.

Author: ericallam

.changeset/tidy-mailboxes-wait.md

@@ -7,6 +7,8 @@ Fixes a case where a chat could silently lose a message. If a message arrived wh
 
 Fixes a recovered answer being cut off. After a crash the agent replays the message it had not answered yet, but it was replaying the stop that arrived after that message too, so the turn answering it was aborted the moment it began. A stop is now only applied to the turn that was live when it arrived. That holds however the stop got there: sent after the last completed turn, or sent to a chat whose most recent turn was completed by an older version of the SDK.
 
+One limitation to know about: the recovered answer is persisted correctly, but a chat page that stayed open across the crash keeps showing the partial answer it had already received. Reload the page to see the full recovered answer.
+
 Also fixes a retried send being answered twice. When a send was retried and its idempotency claim was lost, the agent could consume the same message a second time.
 
 Custom agent loops can now inspect pending chat input without consuming it, and consume one record at a time, with `chat.messages.hasPending()` and `chat.messages.next()`. Records carry stable identifiers so a redelivery is recognisable.