dsh-wake-relay 0.1.1 → 0.1.3

package/README.en.md

@@ -50,12 +50,42 @@ No UI is a deliberate choice: this plugin's user is a script.
 
 ## Install
 
+**The `desktop` profile is owned by the Electron app — the CLI refuses to touch it:**
+
+```
+error: profile "desktop" is managed exclusively by the Electron application
+```
+
+Two paths, then.
+
+**① Let the agent install it (works on desktop and web, recommended)**
+
+Paste this into your DSH:
+
+````text
+Install dsh-wake-relay — the external wake bridge on npm. Follow the Install section of its README; do not invent steps.
+
+When done, reply with exactly three lines: profile name / actual port / the raw GET /health response.
+
+The only proof it installed is a new `listening` line in $DSH_HOME/wake-bridge.log. `install_bundle` returning `applied` is not proof — it says that even when nothing loaded.
+````
+
+**② Command line (profiles not owned by Electron, e.g. `dsh web`)**
+
+```bash
+dsh plugin --profile web add dsh-wake-relay
+```
+
+From a local clone:
+
 ```bash
-dsh plugin --profile desktop add dsh-wake-relay     # from npm
-dsh plugin --profile <your-profile> add ./dsh-wake-relay   # from a local clone
+git clone https://github.com/tendayst/dsh-wake-relay
+dsh plugin --profile web add ./dsh-wake-relay
 ```
 
-Restart DSH afterwards — the plugin tree is composed at process start.
+Installing usually takes effect **immediately** (`plugin_manager` applies it live; no restart needed). The only reliable check is whether `wake-bridge.log` gained a new `listening` line — if not, restart DSH once.
+
+> **Do not install a second wake plugin alongside this one.** They all publish to the same `$DSH_HOME/wake-endpoint.json`. Two of them fight over the port (the loser falls back to an ephemeral one), and the one that stops can erase the other's discovery file. Since 0.1.2 this plugin only clears that file when it still points at itself, but the port contention remains.
 
 ### Two traps you only hit while installing
 

package/README.md

@@ -46,16 +46,42 @@ UI 是有意的取舍：这个插件的读者是**脚本**，不是人的眼睛
 
 ## 安装
 
+**桌面版的 `desktop` profile 由 Electron 独占，命令行装不了**——`dsh plugin --profile desktop add …` 会直接报错：
+
+```
+error: profile "desktop" is managed exclusively by the Electron application
+```
+
+所以分两种路径。
+
+**① 让 AI 装（桌面版 / Web 版都适用，推荐）**
+
+把这段粘给你的 DSH，它会自己装好并验证：
+
+````text
+帮我装 dsh-wake-relay —— npm 上的 DSH 外部唤醒桥。照它 README 的「安装」那节来，别自己发明步骤。
+
+装好只回三行：profile 名 / 实际端口 / GET /health 的返回。
+
+判据只有一条：$DSH_HOME/wake-bridge.log 里多了一行 listening 才算装上。install_bundle 返回 applied 不算——它没加载也这么说。
+````
+
+**② 命令行（`dsh web` 这类非 Electron 管理的 profile）**
+
 ```bash
-# 从 npm（发布后）
-dsh plugin --profile desktop add dsh-wake-relay
+dsh plugin --profile web add dsh-wake-relay
+```
 
-# 从本地目录
-git clone <repo> dsh-wake-relay
-dsh plugin --profile <你的 profile> add ./dsh-wake-relay
+从本地目录装：
+
+```bash
+git clone https://github.com/tendayst/dsh-wake-relay
+dsh plugin --profile web add ./dsh-wake-relay
 ```
 
-装完**重启 DSH** 生效（插件树在进程启动时组合）。
+装完通常**即时生效**（`plugin_manager` 会动态 apply，不用重启）。判断标准只有一条：`wake-bridge.log` 里有没有新的 `listening` 行。没有就重启一次 DSH。
+
+> **不要同时装第二个唤醒插件。** 所有实现都写同一个 `$DSH_HOME/wake-endpoint.json`。两个同时跑会抢端口（后启动的那个退到随机端口），而停止时写的 `port: null` 会让另一个的发现文件失效——0.1.2 起本插件只在文件仍指向自己时才清空，但端口之争依然存在。
 
 ### 两个装的时候才会遇到的陷阱
 

package/index.js

@@ -533,6 +533,18 @@ export function apply(ctx, config) {
       } catch {
         /* ignore */
       }
+      // Two wake plugins can share one $DSH_HOME, and they all publish to the
+      // same endpoint path. Only erase the discovery file if it still describes
+      // this instance — otherwise the one that stops last blinds the other.
+      try {
+        const current = JSON.parse(readFileSync(ENDPOINT_PATH, "utf8"));
+        if (Number(current.port) !== Number(listenPort)) {
+          log(`stopped; left the endpoint file alone (it belongs to port ${current.port})`);
+          return;
+        }
+      } catch {
+        /* no endpoint file: nothing to guard */
+      }
       try {
         writeFileSync(ENDPOINT_PATH, JSON.stringify({ port: null, stoppedAt: new Date().toISOString() }), "utf8");
       } catch {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-wake-relay",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "Let any external process wake a DeepSeek Harness session — with synchronous delivery semantics, so the caller can own the retry loop and fire events that happened while the host was down.",
   "type": "module",
   "main": "./index.js",