dsh-ai-terminal-pet 1.2.13 → 1.2.15

package/README.md

@@ -91,10 +91,10 @@ tarball, or by pinning the release tag. All three are verified end to end:
 dsh plugin --profile <profile> add dsh-ai-terminal-pet
 
 # release tarball: same bytes as the npm release, straight from the GitHub Release
-dsh plugin --profile <profile> add https://github.com/jjjjjjjjnnjnn/ai-terminal-pet/releases/download/dsh-plugin-v1.2.13/dsh-ai-terminal-pet-1.2.13.tgz
+dsh plugin --profile <profile> add https://github.com/jjjjjjjjnnjnn/ai-terminal-pet/releases/download/dsh-plugin-v1.2.15/dsh-ai-terminal-pet-1.2.15.tgz
 
 # git source, pinned to the release tag
-dsh plugin --profile <profile> add "git+https://github.com/jjjjjjjjnnjnn/ai-terminal-pet.git#dsh-plugin-v1.2.13&path:/packages/dsh-ai-terminal-pet"
+dsh plugin --profile <profile> add "git+https://github.com/jjjjjjjjnnjnn/ai-terminal-pet.git#dsh-plugin-v1.2.15&path:/packages/dsh-ai-terminal-pet"
 ```
 
 Those three differ only in transport. The npm path is the shortest and the one a
@@ -169,7 +169,16 @@ only wants the plugin gets one installed automatically.
 ## Requirements and limits
 
 - Windows only (named pipes plus a Win32 layered window).
-- Node 22.19+ or 24+ in the Harness runtime.
+- DeepSeek Harness 0.2.x. `engines.dsh` is `>=0.2.0-0 <0.3.0-0`, and since DSH
+  0.2.1-alpha.3 the host reads that range alone: a bundle whose range the running
+  DSH does not satisfy is refused and the profile rolled back, so the range is the
+  whole compatibility statement. The `-0` bounds are deliberate - DSH evaluates
+  the range with semver's `includePrerelease`, under which `<0.3.0` still admits
+  `0.3.0-rc.1` and `>=0.2.0` still refuses `0.2.0-rc.1`. Both ends were measured
+  against the host's own compatibility function. It was verified by installing
+  this tarball into a real 0.2.0-rc.1 host and a real 0.2.2-rc.3 host and
+  composing its layer with `dsh --dump-config`.
+- Node 24.9+ in the Harness runtime, which is what DSH 0.2.x itself requires.
 - Nothing in this package can fail the host: every entry point is wrapped,
   every report is fire-and-forget, and there is no process.exit.
 - Session id is the Harness session.header.id; pid is a synthetic per-session

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-ai-terminal-pet",
-  "version": "1.2.13",
+  "version": "1.2.15",
   "description": "DeepSeek Harness Cordis bundle that mirrors session state into the AI Terminal Pet desktop overlay (Windows).",
   "license": "MIT",
   "type": "module",
@@ -25,8 +25,8 @@
   ],
   "icon": "./icon.png",
   "engines": {
-    "node": "^22.19 || >=24",
-    "dsh": ">=0.1.0-rc.6"
+    "node": ">=24.9.0",
+    "dsh": ">=0.2.0-0 <0.3.0-0"
   },
   "dsh": {
     "bundle": {

package/vendor/manifest.json

@@ -3,13 +3,13 @@
   "generatedBy": "scripts/vendor.mjs",
   "goVersion": "go1.27.0",
   "source": {
-    "files": 35,
-    "sha256": "597be5e59ec58c61fee1a19db23c6a7ea1ca53292be6588b0c455a1e55fe20c1"
+    "files": 36,
+    "sha256": "a841b09b52bba55db8f294dc55e727b186258b90a8d238a57c7a6fb84997b134"
   },
   "overlay": {
     "file": "vendor/AI-Terminal-Pet.exe",
-    "bytes": 4520448,
-    "sha256": "562d1565c8b80739144a795beecbcb78551a15ef8a01e4342588e4836ccd28fd"
+    "bytes": 4554240,
+    "sha256": "01b42dc27c06413be7120f9cc5be0430aca29546f660a6c30d1f4a0e3ed84bdb"
   },
   "protocol": {
     "file": "vendor/protocol.js",