dsh-ntr 0.1.2 → 0.1.3

package/README.en.md

@@ -58,6 +58,8 @@ dsh plugin --profile web add ./
 
 To upgrade later: `git pull` → `npm run build` → restart `dsh web`. `add .` installs the directory as `link:`, so a rebuild plus a restart picks up the changes — no re-add needed.
 
+> Before switching from the source install to the npm/market build, uninstall the old version and delete `node_modules/dsh-ntr` from the profile. pnpm's hoisted layout leaves the linked checkout's `node_modules` inside the package directory, and the stale dependencies shadow the newly installed SDK — see the `EPERM ... zod` entry in the FAQ.
+
 > `dsh plugin` is a pnpm forwarder — `--profile <name>` is required, and `add .` installs the current directory as `link:`. The official desktop app's profile is owned by its own plugin manager; don't run the CLI against it.
 
 ---
@@ -194,6 +196,10 @@ That's the agent's own permission mode; the option text comes straight from it.
 
 Normal. Mode lists are declared by each agent itself (sent via `session/set_mode`); the plugin lists them verbatim — no unified translation, no defaults filled in. To change the wording, edit the agent's own config.
 
+**Activation fails with `EPERM ... zod` after switching from the source install to npm / the market?**
+
+That's stale dependency state, not a missing plugin file: the failing path will contain `node_modules/dsh-ntr/node_modules/.pnpm/...`. The source install uses `link:` to your checkout; pnpm's hoisted layout replaces the package directory with the registry files but leaves the link target's `node_modules` behind. That old tree (an older `@agentclientprotocol/sdk` plus its broken `zod` symlink) shadows the freshly installed dependency, so DSH's import hits the bad link and fails with `EPERM`. Fix: uninstall `dsh-ntr` in the plugin manager, remove `~/.dsh/profiles/<profile>/node_modules/dsh-ntr` (or just its nested `node_modules`), then reinstall and restart. For the desktop app's profile, uninstall/reinstall from the app's Plugins page instead of the CLI.
+
 ---
 
 ## What it can do (feature list)

package/README.md

@@ -58,6 +58,8 @@ dsh plugin --profile web add ./
 
 之后升级：`git pull` → `npm run build` → 重启 `dsh web`。`add .` 以 `link:` 方式安装，重建后重启即生效，不需要重新 add。
 
+> 从源码安装切到 npm / 市场版前，先在插件管理器里卸载旧版，并删掉 profile 里的 `node_modules/dsh-ntr`。pnpm 的 hoisted 布局会把 `link:` 目标里的 `node_modules` 留在包目录内，旧依赖会遮蔽新装的 SDK，典型报错见「常见问题」里的 `EPERM ... zod`。
+
 > `dsh plugin` 是 pnpm 转发器，`--profile <name>` 必填；`add .` 会把当前目录以 `link:` 方式装进 profile。官方桌面 App 的 profile 由它自己的插件管理器掌管，不要对着它的 profile 跑命令行。
 
 ---
@@ -194,6 +196,10 @@ agent 要动敏感的东西时会问你。审批卡直接出现在聊天输入
 
 正常。模式清单由每个 agent 自己声明（`session/set_mode` 下发），插件照原样列出，不统一翻译、也不补默认值。想改叫法要在 agent 自己的配置里改。
 
+**从源码安装切到 npm / 市场版后，启用时报 `EPERM ... zod`？**
+
+这是旧依赖残留，不是插件缺文件：错误路径里会出现 `node_modules/dsh-ntr/node_modules/.pnpm/...`。源码安装用 `link:` 指向你的仓库；pnpm 的 hoisted 布局在切到 registry 版时会把包目录换成真实文件，但会留下链接目标里的 `node_modules`。这份旧树（旧版 `@agentclientprotocol/sdk` 及其失效的 `zod` 软链）会遮蔽新装的依赖，DSH 导入时 stat 到坏链就报 `EPERM`。处理：在插件管理器里卸载 `dsh-ntr`，删除 `~/.dsh/profiles/<profile>/node_modules/dsh-ntr`（或只删它下面的 `node_modules`），再重装并重启。桌面 App 的 profile 请直接在 App 的插件页卸载/重装，不要用命令行。
+
 ---
 
 ## 它能做什么（能力清单）

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-ntr",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Interactive Agent Client Protocol (ACP) client for the DSH web UI: attach any ACP-capable agent and stream its session.",
   "repository": "https://github.com/GDWhisper/dsh-ntr.git",
   "type": "module",
@@ -34,7 +34,8 @@
     "prepack": "npm run typecheck && npm test && npm run build"
   },
   "dependencies": {
-    "@agentclientprotocol/sdk": "^1.4.0"
+    "@agentclientprotocol/sdk": "^1.4.0",
+    "zod": "^3.25.0 || ^4.0.0"
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "4.0.2",