Say in the changelog that a live-screen reconnect stops killing itself

Author: beardthelion

CHANGELOG.md

@@ -8,6 +8,19 @@ Newest first. `Unreleased` is what is on `main` and not yet tagged.
 
 ## Unreleased
 
+### Reconnecting a live screen no longer stops the screen you just reconnected
+
+A Bot's screen allows one viewer, and opening a second `/stream` replaces the first. The replaced
+socket is left open, because it belongs to a client that may still be using it, so on an ordinary
+reconnect, where the browser opens the new connection before dropping the old one, the old socket
+closed after the new one was already casting. Closing it stopped the session's viewer without asking
+whether the closing socket was the one casting, so it stopped the replacement.
+
+Both halves were silent. The screen stopped updating, and anything typed afterwards was dropped
+without a word, because the input path looks for a viewer before it looks for anything it can report.
+
+A close now stops casting only when the socket closing is the one that was casting.
+
 ## 0.0.4
 
 ### A click citing a ref this deployment cannot resolve is refused