dsh-vscode-workbench 0.1.11 → 0.1.12

package/README.en.md

@@ -64,7 +64,7 @@ The workbench mounts through the official `sidebar.footer.action` and `shell.ove
 
 ## Installation
 
-Plugin 0.1.11 targets DeepSeek Harness `0.2.1-rc.5` (Cordis `4.0.5`). Update Harness before installing; see the table below for older plugin versions.
+Plugin 0.1.12 targets DeepSeek Harness `0.2.1-rc.5` (Cordis `4.0.5`). Update Harness before installing; see the table below for older plugin versions.
 
 ```bash
 npm i -g @deepseek-ai/dsh@0.2.1-rc.5
@@ -74,6 +74,22 @@ npm i -g @deepseek-ai/dsh@0.2.1-rc.5
 dsh plugin --profile web add dsh-vscode-workbench
 ```
 
+Installing from the DSH Plugins page or a marketplace also adds the package to `dsh.profile.bundles` and enables it. The CLI command above only writes `dependencies`, so add `dsh-vscode-workbench` to `dsh.profile.bundles` in `~/.dsh/profiles/web/package.json` and restart `dsh web`:
+
+```json
+{
+  "dsh": {
+    "profile": {
+      "bundles": [
+        "@deepseek-ai/dsh-base",
+        "@deepseek-ai/dsh-web-app",
+        "dsh-vscode-workbench"
+      ]
+    }
+  }
+}
+```
+
 ### First terminal installation
 
 The terminal uses `node-pty`. If installation reports a blocked build script, merge the following into `~/.dsh/profiles/web/pnpm-workspace.yaml` on the DSH host, preserving existing settings:
@@ -122,12 +138,13 @@ The plugin marketplace files this under the generic `plugin-side install failure
 
 | Plugin version | Required Harness |
 | --- | --- |
+| 0.1.12 | `0.2.1-rc.5` (Cordis `4.0.5`, default baseline); also checked with `0.2.2-rc.1` (Cordis `4.1.0`, Node.js ≥24.9) |
 | 0.1.11 | `0.2.1-rc.5` (Cordis `4.0.5`, default baseline); also checked with `0.2.2-rc.1` (Cordis `4.1.0`, Node.js ≥24.9) |
 | 0.1.10 | `0.2.1-rc.4` (Cordis `4.0.5`, previous validation baseline) |
 | 0.1.9 | `0.2.1-alpha.3` (Cordis `4.0.5-alpha.2`, previous validation baseline) |
 | 0.1.8 | `0.1.1-rc.2` |
 
-No plugin version runs on Harness `0.2.0-rc.2`: 0.1.9 needs the `workingDirectory` service that first shipped in Harness `0.2.1-alpha.2`, while 0.1.8 only targets `0.1.1-rc.2`. Update Harness to `0.2.1-rc.5` before installing plugin 0.1.11, for example with a global npm install:
+No plugin version runs on Harness `0.2.0-rc.2`: 0.1.9 needs the `workingDirectory` service that first shipped in Harness `0.2.1-alpha.2`, while 0.1.8 only targets `0.1.1-rc.2`. Update Harness to `0.2.1-rc.5` before installing plugin 0.1.12, for example with a global npm install:
 
 ```bash
 npm i -g @deepseek-ai/dsh@0.2.1-rc.5
@@ -141,6 +158,8 @@ Version 0.1.11 updates DSH development dependencies and peers to `0.2.1-rc.5`, k
 
 Both dependency environments pass type checking, 52 tests and the build, covering the official version gate, real Harness cookie authentication and session-directory switching regressions. Full DSH browser end-to-end validation has not been run. The next channel requires Node.js ≥24.9.
 
+Version 0.1.12 focuses on reliability and macOS usability. It preserves and restores unsaved workspace drafts, hardens concurrent saves and file operations, adds a draggable title bar with correct window clearance, and hides the native DSH sidebar chrome while the workbench is active. WebSocket URLs now follow the DSH transport, and terminal startup repairs the `spawn-helper` execute bits. PDF, DOCX, image and Markdown previews were verified in DSH Desktop.
+
 - Client contributions use `ui-renderer` slots and select the current session through `ui-session`'s `mainView` retain count, replacing the removed `dsh-client-runtime`.
 - Files, search, Git and new terminals use `workingDirectory.get(session)`. Workspace selection follows the working-directory projection; missing sessions return 404.
 - HTTP and WebSocket routes share Harness authentication and Host/Origin checks through `connection.requestRejection()`. Terminals also require loopback access.

package/README.md

@@ -64,7 +64,7 @@
 
 ## 安装
 
-插件 0.1.11 适配 DeepSeek Harness `0.2.1-rc.5`（Cordis `4.0.5`）。请先更新 Harness，再安装插件；旧版对应关系见下表。
+插件 0.1.12 适配 DeepSeek Harness `0.2.1-rc.5`（Cordis `4.0.5`）。请先更新 Harness，再安装插件；旧版对应关系见下表。
 
 ```bash
 npm i -g @deepseek-ai/dsh@0.2.1-rc.5
@@ -74,6 +74,22 @@ npm i -g @deepseek-ai/dsh@0.2.1-rc.5
 dsh plugin --profile web add dsh-vscode-workbench
 ```
 
+通过 DSH 插件页或插件市场安装时，界面会把它加入 `dsh.profile.bundles` 并启用。用上面的 CLI 命令安装时只写入 `dependencies`，还需要在 `~/.dsh/profiles/web/package.json` 的 `dsh.profile.bundles` 中加入 `dsh-vscode-workbench`，然后重启 `dsh web`：
+
+```json
+{
+  "dsh": {
+    "profile": {
+      "bundles": [
+        "@deepseek-ai/dsh-base",
+        "@deepseek-ai/dsh-web-app",
+        "dsh-vscode-workbench"
+      ]
+    }
+  }
+}
+```
+
 ### 首次安装终端支持
 
 终端使用 `node-pty`。如果安装日志提示其构建脚本被阻止，在 DSH 所在机器的 `~/.dsh/profiles/web/pnpm-workspace.yaml` 中合并以下配置，保留已有设置：
@@ -122,12 +138,13 @@ dsh: nothing was installed.
 
 | 插件版本 | 需要的 Harness |
 | --- | --- |
+| 0.1.12 | `0.2.1-rc.5`（Cordis `4.0.5`，默认基线）；另验证 `0.2.2-rc.1`（Cordis `4.1.0`，Node.js ≥24.9） |
 | 0.1.11 | `0.2.1-rc.5`（Cordis `4.0.5`，默认基线）；另验证 `0.2.2-rc.1`（Cordis `4.1.0`，Node.js ≥24.9） |
 | 0.1.10 | `0.2.1-rc.4`（Cordis `4.0.5`，旧版验证基线） |
 | 0.1.9 | `0.2.1-alpha.3`（Cordis `4.0.5-alpha.2`，旧版验证基线） |
 | 0.1.8 | `0.1.1-rc.2` |
 
-Harness `0.2.0-rc.2` 上没有可用的插件版本：0.1.9 依赖 Harness `0.2.1-alpha.2` 才引入的 `workingDirectory` 服务，0.1.8 又只适配 `0.1.1-rc.2`。请先把 Harness 升级到 `0.2.1-rc.5` 再安装 0.1.11，例如 npm 全局安装时：
+Harness `0.2.0-rc.2` 上没有可用的插件版本：0.1.9 依赖 Harness `0.2.1-alpha.2` 才引入的 `workingDirectory` 服务，0.1.8 又只适配 `0.1.1-rc.2`。请先把 Harness 升级到 `0.2.1-rc.5` 再安装 0.1.12，例如 npm 全局安装时：
 
 ```bash
 npm i -g @deepseek-ai/dsh@0.2.1-rc.5
@@ -141,6 +158,8 @@ npm i -g @deepseek-ai/dsh@0.2.1-rc.5
 
 两套依赖环境均通过类型检查、52 项测试及构建，覆盖官方版本闸门、真实 Harness cookie 认证与会话目录切换回归；尚未完成完整 DSH 页面端到端验证。next 渠道需 Node.js ≥24.9。
 
+0.1.12 在此基础上集中修复可靠性与 macOS 使用问题：保留并恢复工作区草稿，加强并发保存和文件操作；补齐可拖动标题栏与窗口留白，修正活动工作台的 DSH 原生侧栏遮挡；WebSocket 地址跟随 DSH transport，终端启动时自动修复 `spawn-helper` 执行位。PDF、DOCX、图片和 Markdown 预览已在 DSH Desktop 中实际验证。
+
 - 客户端通过 `ui-renderer` 提供的槽位服务注册界面，使用 `ui-session` 的 `mainView` 引用选择当前会话；不再依赖已移除的 `dsh-client-runtime`。
 - 文件、搜索、Git 和新建终端通过 `workingDirectory.get(session)` 使用会话当前目录，跟随工作目录投影切换；失效会话返回 404。
 - HTTP 与 WebSocket 接口使用 `connection.requestRejection()`，共享 Harness 登录认证及 Host/Origin 校验；终端额外保留 loopback 限制。