dsh-wake-relay 0.1.0 → 0.1.2

package/README.en.md

@@ -55,7 +55,9 @@ dsh plugin --profile desktop add dsh-wake-relay     # from npm
 dsh plugin --profile <your-profile> add ./dsh-wake-relay   # from a local clone
 ```
 
-Restart DSH afterwards — the plugin tree is composed at process start.
+Installing from npm 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

@@ -55,7 +55,9 @@ git clone <repo> dsh-wake-relay
 dsh plugin --profile <你的 profile> add ./dsh-wake-relay
 ```
 
-装完**重启 DSH** 生效（插件树在进程启动时组合）。
+从 npm 装通常**即时生效**（`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.0",
+  "version": "0.1.2",
   "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",