From 16a59432459089fbc1ea198ca025fb620501a19a Mon Sep 17 00:00:00 2001
From: ShineBreaker <102544159+ShineBreaker@users.noreply.github.com>
Date: Wed, 11 Nov 2026 19:39:53 +0800
Subject: [PATCH] fix(dsh): declare @deepseek-ai/dsh-tools as a host peer
 dependency

The dsh runtime resolves @deepseek-ai/dsh-* packages from its own
installation, so declaring dsh-tools as a regular dependency installs a
second copy beside the host's. On a 0.2.2-rc.1 install this pulled in
dsh-tools 0.2.0-rc.2 under the plugin's node_modules, putting two
different tool-registry implementations in one process; dsh-market also
flags it as a shared-host-package-dependency warning.

Follow the upstream packaging rule: packages whose instances must be
shared with the host belong under peerDependencies (compatibility
checking and runtime resolution) and devDependencies (local tests).
---
 plugins/dsh/package.json | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/plugins/dsh/package.json b/plugins/dsh/package.json
index 17b24cd8..f71ba5b0 100644
--- a/plugins/dsh/package.json
+++ b/plugins/dsh/package.json
@@ -30,15 +30,18 @@
     }
   },
   "dependencies": {
-    "@deepseek-ai/dsh-tools": ">=0.1.1-rc.2 <0.2.0 || >=0.2.0-rc.1 <0.3.0",
     "@deepseek-ai/schemastery": "^3.18.1"
   },
   "peerDependencies": {
-    "@deepseek-ai/cordis": "^4.0.1"
+    "@deepseek-ai/cordis": "^4.0.1",
+    "@deepseek-ai/dsh-tools": ">=0.1.1-rc.2 <0.2.0 || >=0.2.0-rc.1 <0.3.0"
   },
   "peerDependenciesMeta": {
     "@deepseek-ai/cordis": {
       "optional": true
     }
+  },
+  "devDependencies": {
+    "@deepseek-ai/dsh-tools": ">=0.1.1-rc.2 <0.2.0 || >=0.2.0-rc.1 <0.3.0"
   }
 }