chore: v0.49.1

Cargo.toml

@@ -48,7 +48,7 @@ categories = ["network-programming", "web-programming::http-server"]
 
 # 二进制走 CalVer，crate 走 SemVer —— 两者是两回事，卖给不同的人。
 # 这里是 crate 的版本。
-version = "0.49.0"
+version = "0.49.1"
 
 [workspace.dependencies]
 # ── 内部 crate ───────────────────────────────────────────

release-notes/0.49.1.md

@@ -0,0 +1,11 @@
+This release changes only the server guide, [docs/server.md](https://github.com/ThinkWatchProject/ThinkWatch-Core/blob/main/docs/server.md) and its Chinese version, so that it describes the desktop app's side of a remote connection as the app behaves. The binaries behave as in 0.49.0.
+
+**Upgrade notes**
+
+- The control-plane protocol version is unchanged (22) and so is the request store's schema (20). A server on 0.49.0 does not need to upgrade, and ThinkWatch Lite 2026.9.17, which includes 0.49.0, connects to 0.49.0 and 0.49.1 alike.
+
+**Connecting from the desktop app.** The guide names the settings section Connection and the Add remote connection dialog, which also asks for a name. Test connection tests without saving, Save and switch tests before it saves and asks before it switches, and Save stores the connection untested; switching to a remote connection always tests it first and stays on the current connection if the test fails.
+
+**Which version a server runs.** The app connects only to a core that speaks its control-plane protocol version, which in practice means the core version the app includes, and the latest release can be newer than that. The guide therefore installs and switches with `--version <version>`, notes that `twcore upgrade --version` also installs an older release, and says that recent versions of the app (2026.9.17 and later) show `sudo twcore upgrade --version <version> --restart` with the version they need when the versions differ. It also says that `twcore upgrade` leaves the data alone, while a version whose request store has another schema starts with an empty request history.
+
+**While connected to a remote core.** The guide adds that the app signs ChatGPT accounts in with a device code only, next to the three things a remote connection cannot do.