docs(release): correct the /new MCP handoff entry in the 0.10.2 notes

0b2f5022f4 said that after /new "HTTP/SSE, plugin and runtime-added
servers reconnect". Only HTTP/SSE servers reconnect. Servers added at
runtime and plugin-contributed servers are conversation capabilities and
are closed: a new pool starts with an empty dynamic_servers map
(crates/tui/src/mcp.rs), as docs/MCP.md already says. The entry now matches
MCP.md, and it states that /resume <id>, /load and provider or workspace
switches still restart every server. A read-only design review of the
engine-respawn handoff found the mismatch.

crates/tui/CHANGELOG.md is regenerated with scripts/sync-changelog.sh.

Verification on this tree:
- check-versions.sh --require-dated-release: exit 0.
- npm test: 547 Node tests (540 passed, 7 skipped, 0 failed) and 772
  Vitest passed. npm run check:web: exit 0.

Refs CW-7430

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01NBKbhx19BRbZtvWK8rVKjz

CHANGELOG.md

@@ -72,11 +72,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   how many are not connected out of the configured total.
 - `/new` keeps configured stdio MCP servers running: the next conversation
   adopts each live process when its workspace, MCP backend and server config
-  are unchanged, and dials only what is missing. HTTP/SSE, plugin and
-  runtime-added servers reconnect so they pick up current credentials and
-  network policy. After a provider or workspace switch, `/resume` or `/load`,
-  the MCP panel and `/mcp` show the new engine's status instead of staying
-  stale (CW-7430).
+  are unchanged, and dials only what is missing. HTTP/SSE servers reconnect
+  so they pick up current credentials and network policy; servers added at
+  runtime and plugin-contributed servers are closed with the conversation.
+  `/resume <id>`, `/load` and a provider or workspace switch still restart
+  every server, and the MCP panel and `/mcp` now show the new engine's status
+  instead of staying stale (CW-7430).
 - Resuming a session whose offline queue still holds unsent messages now shows
   a warning naming how many will send after your next message and how to drop
   them with `/queue clear`; it previously hid behind the resume notice. A

crates/tui/CHANGELOG.md

@@ -72,11 +72,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   how many are not connected out of the configured total.
 - `/new` keeps configured stdio MCP servers running: the next conversation
   adopts each live process when its workspace, MCP backend and server config
-  are unchanged, and dials only what is missing. HTTP/SSE, plugin and
-  runtime-added servers reconnect so they pick up current credentials and
-  network policy. After a provider or workspace switch, `/resume` or `/load`,
-  the MCP panel and `/mcp` show the new engine's status instead of staying
-  stale (CW-7430).
+  are unchanged, and dials only what is missing. HTTP/SSE servers reconnect
+  so they pick up current credentials and network policy; servers added at
+  runtime and plugin-contributed servers are closed with the conversation.
+  `/resume <id>`, `/load` and a provider or workspace switch still restart
+  every server, and the MCP panel and `/mcp` now show the new engine's status
+  instead of staying stale (CW-7430).
 - Resuming a session whose offline queue still holds unsent messages now shows
   a warning naming how many will send after your next message and how to drop
   them with `/queue clear`; it previously hid behind the resume notice. A