dsh-session-bridge 0.3.0 → 0.3.2-alpha.1

package/README.md

@@ -119,13 +119,22 @@ time — not just its final reply — and act on it:
 # type-check + bundle the host build + pack a tgz (DSH_CHECKOUT points at the dsh source checkout)
 bash scripts/build.sh && npm run build:client
 
+# type-check src/ against the dsh that is actually installed (no checkout needed)
+npm run check:compat
+
 # via the injector toolchain
 dev_build_plugin dsh-session-bridge
 ```
 
 `build.sh` type-links against a local DSH checkout and is only for local dev.
+That checkout frequently lags the harness the plugin is loaded into, so a green
+`build.sh` does **not** prove the plugin works on the running DSH — `build.sh`
+warns when the two versions differ. Use `npm run check:compat` for that: it
+type-checks `src/` against the `lib/types/*.d.ts` shipped inside the installed
+DSH package, which is the exact API surface the plugin loads against.
+
 The GitHub Actions CI (`ci.yml`) instead resolves the `@deepseek-ai/dsh-*`
-prereleases from the registry — pinned to the `0.1.2-alpha.2` line, which is
+prereleases from the registry — pinned to the `0.1.6-alpha.1` line, which is
 the DSH API surface this code targets — then runs `pnpm typecheck` and
 `pnpm build:client` (the self-contained `tsdown` bundle). Bump that pin
 together with the code when you migrate to a newer DSH API.
@@ -149,6 +158,14 @@ publishing.
 npx -p @deepseek-ai/dsh dsh plugin --profile web add dsh-session-bridge
 ```
 
+A prerelease tag (`v0.3.2-alpha.1`) is published to its own dist-tag (`alpha`,
+`beta`, `rc`) instead of `latest`, so it cannot displace the stable release for
+other users. Opt in explicitly:
+
+```bash
+npx -p @deepseek-ai/dsh dsh plugin --profile web add dsh-session-bridge@alpha
+```
+
 pnpm installs the published tarball and runs its `prepare` script (`tsdown`) to
 ensure `lib/` is present, then `dsh` activates the bundle.
 

package/README.zh.md

@@ -87,10 +87,19 @@
 # 类型检查 + 打包 host bundle + 生成 tgz（DSH_CHECKOUT 指向 dsh 源码 checkout）
 bash scripts/build.sh && npm run build:client
 
+# 针对"实际安装的 dsh"做类型检查（不需要 checkout）
+npm run check:compat
+
 # 或经注入器工具链
 dev_build_plugin dsh-session-bridge
 ```
 
+`build.sh` 按本地 dsh 源码 checkout 做类型链接，仅用于本地开发。该 checkout 常常
+落后于插件实际加载进的 harness，因此 `build.sh` 通过**并不**代表插件在运行中的
+DSH 上可用——两者版本不一致时 `build.sh` 会给出警告。要验证运行版本请用
+`npm run check:compat`：它按已安装 DSH 包内随附的 `lib/types/*.d.ts`（即插件真正
+加载的 API 面）对 `src/` 做类型检查。
+
 ## 部署
 
 DSH web 从活动 profile 加载外部插件。本包是一个 **bundle**：`package.json` 声明了
@@ -107,6 +116,13 @@ DSH web 从活动 profile 加载外部插件。本包是一个 **bundle**：`pac
 npx -p @deepseek-ai/dsh dsh plugin --profile web add dsh-session-bridge
 ```
 
+预发布标签（`v0.3.2-alpha.1`）会发布到自己的 dist-tag（`alpha`/`beta`/`rc`），
+而不会占用 `latest`，因此不会顶掉其他用户使用的稳定版。需要显式选用：
+
+```bash
+npx -p @deepseek-ai/dsh dsh plugin --profile web add dsh-session-bridge@alpha
+```
+
 pnpm 会安装发布的 tarball 并运行其 `prepare` 脚本（`tsdown`）以确保 `lib/` 就绪，
 随后 `dsh` 激活该 bundle。
 

package/dsh.plugin.json

@@ -1,10 +1,10 @@
 {
   "id": "dsh-external/dsh-session-bridge",
-  "version": "0.3.0",
+  "version": "0.3.2-alpha.1",
   "main": "./lib/index.js",
   "description": "会话桥：创建主会话 / 向任意会话发消息 / 等待回复 / 读取消息 / 按名或 id 查找会话（支持跨工作区）；另含监控/调度主任务与归档会话。",
   "engines": {
-    "dsh": "^0.1.0-rc.6 || ^0.1.1-0 || ^0.1.2-0"
+    "dsh": "^0.1.0-rc.6 || ^0.1.1-0 || ^0.1.2-0 || ^0.1.5-0 || ^0.1.6-0"
   },
   "contributes": {
     "tools": [