@aiwayds/dsh-mcp-adapter 0.4.0 → 0.4.1

package/README.md

@@ -54,6 +54,18 @@ Or directly from git:
 dsh plugin --profile <name> add github:fan56/dsh-mcp-adapter
 ```
 
+## Uninstall
+
+```
+dsh plugin --profile <name> remove @aiwayds/dsh-mcp-adapter
+```
+
+The host reconciles the profile automatically: the `dsh.profile.bundles` entry is spliced out and the package's patch layer drops.
+
+One thing deliberately **stays**: the `mcp-adapter:` section in `~/.dsh/settings.yaml` — the stable server ids (`1..99`) and the disabled gates. It is never pruned by design: if you reinstall the plugin, every server keeps the same id it had before.
+
+To purge that state too, delete the `mcp-adapter:` section from `settings.yaml` yourself; ids will be re-allocated from scratch on reinstall.
+
 ## Config
 
 | key | default | meaning |

package/README.zh.md

@@ -46,6 +46,18 @@
 dsh plugin --profile <name> add @aiwayds/dsh-mcp-adapter
 ```
 
+## 卸载
+
+```
+dsh plugin --profile <name> remove @aiwayds/dsh-mcp-adapter
+```
+
+宿主会自动完成清理：`dsh.profile.bundles` 里对应的条目被拼接移除，插件的 patch 层随之失效。
+
+有一份状态被刻意**保留**：`~/.dsh/settings.yaml` 里的 `mcp-adapter:` 小节——stable server id（1..99）和 disabled 门闩。它按设计永不回收：重装本插件后，每个 server 仍沿用之前的 id。
+
+连这份状态也想清掉的话，请自行删除 `settings.yaml` 里的 `mcp-adapter:` 小节；重装时 id 会重新分配。
+
 ## 配置
 
 | 键 | 默认值 | 含义 |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aiwayds/dsh-mcp-adapter",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "dsh plugin: token-efficient prompt-side shim for the official MCP client — folds mcp__* tool schemas out of every assembled prompt and exposes two constant meta-tools (mcp_list / mcp_call) instead",
   "keywords": [
     "dsh",

package/scripts/smoke-boot.mjs

@@ -11,9 +11,11 @@
 //   5. a real boot under a timeout must load the plugin tree without a
 //      loader error (a healthy boot is silent and survives to the kill
 //      signal; a broken plugin dies within ~1s with the loader error)
+//   6. `dsh plugin --profile smoke remove <pkg>` must reconcile the profile
+//      back to stock — the post-removal dump no longer contains the entry
 //
-// Exit 0 = mounted and boots clean. Temp dir is kept and printed on failure,
-// removed on success.
+// Exit 0 = mounted, boots clean, and removal restores the stock tree. Temp
+// dir is kept and printed on failure, removed on success.
 //
 // dsh-mcp-adapter note: with no MCP servers configured the meta-tools mount
 // but nothing folds (idle); the smoke proves the plugin LOADS and APPLIES —
@@ -104,5 +106,14 @@ if (boot.signal !== 'SIGKILL' && boot.status !== 0) {
   fail(`dsh exited early with code ${boot.status} and no loader error — unexpected`, output)
 }
 
-console.log(`smoke-boot: PASS — ${ownName} composed into the scratch profile tree and booted clean in real dsh (${boot.signal === 'SIGKILL' ? `survived ${bootSeconds}s boot window` : `exited ${boot.status}`})`)
+// Phase 3 — uninstall leg: removal must reconcile the profile tree back to stock.
+const remove = spawnSync('dsh', ['plugin', '--profile', 'smoke', 'remove', ownName], { cwd: profile, encoding: 'utf8', env: dshEnv })
+if (remove.status !== 0 || remove.error) fail('dsh plugin remove failed', `${remove.stdout}\n${remove.stderr}`)
+const dumpAfter = spawnSync('dsh', ['--profile', 'smoke', '--dump-config'], { cwd: profile, encoding: 'utf8', env: dshEnv })
+if (dumpAfter.status !== 0 || dumpAfter.error) fail('dsh --dump-config failed after removal', `${dumpAfter.stdout}\n${dumpAfter.stderr}`)
+if (dumpAfter.stdout.includes('dsh-mcp-adapter')) {
+  fail('the composed tree still contains the plugin entry after removal', dumpAfter.stdout)
+}
+
+console.log(`smoke-boot: PASS — ${ownName} composed into the scratch profile tree and booted clean in real dsh (${boot.signal === 'SIGKILL' ? `survived ${bootSeconds}s boot window` : `exited ${boot.status}`}); removal restored the stock tree`)
 rmSync(work, { recursive: true, force: true })