dsh-code-server-app 0.3.71 → 0.3.72

package/README.en.md

@@ -536,7 +536,7 @@ data call changes; the caller stays as it is).
   committed hand-written source: there is no build step anywhere on that chain).
 
 > Verified locally (BM: Windows 11 ARM64): the whole tree/dependency chain hangs directly off the plugin's
-> dependency table — the tree package `@jinsiyu/dshcs-vscode-server` (currently 4.139.1, a 44.4 MB tarball),
+> dependency table — the tree package `@jinsiyu/dshcs-vscode-server` (currently 4.141.0, a ~44 MB tarball),
 > the pure-JS inner dependencies plus the 7 platform-independent repacks in `dependencies`, and the 8
 > platform-specific repacks (win32-arm64 / win32-x64) in `optionalDependencies` with their own os/cpu gates;
 > the original names are restored by junctions created at runtime (`lib/native.js`)
@@ -584,7 +584,7 @@ pnpm run promote -- <version>
 | Goal | Command |
 |---|---|
 | **Build from the latest upstream release** | `pnpm run vendor:latest` (= `--force`): pulls `code-server@latest`'s tree into `vendor/vscode`; afterwards you **must** re-run `repack:build` and republish every sub-package |
-| **Pin a version** | `pnpm run vendor:vscode -- --version 4.139.1` |
+| **Pin a version** | `pnpm run vendor:vscode -- --version 4.141.0` |
 | **Snapshot from an existing tree** | `pnpm run vendor:vscode -- --from <code-server dir>` (seconds) |
 | **Rebuild every sub-package** | `pnpm run repack:build -- --target win32-arm64,win32-x64 --pack` (without `--from` it npm-installs and compiles the source tree itself — slow) |
 | **Rebuild only the tree + dependency table** | `node scripts/vendor-repacks.mjs --reuse --target win32-arm64,win32-x64 --pack` (reuses the natives already in `repack/build`; also rewrites `lib/vendored.json` and the plugin dependency table) |
@@ -612,7 +612,7 @@ pnpm run watch:upstream                    # same, but first goes through pnpm's
 node scripts/watch-upstream.mjs --json     # machine readable (what a DSH in-session reminder parses); human output goes to stderr
 node scripts/watch-upstream.mjs --no-notify # report only, no notification (regressions / unattended)
 node scripts/watch-upstream.mjs --fixture f.json # use a local JSON file as the registry response (offline)
-node scripts/watch-upstream.mjs --local 4.140.0  # override the local baseline for a dry run (does not read vendor/)
+node scripts/watch-upstream.mjs --local 4.141.0  # override the local baseline for a dry run (does not read vendor/)
 node scripts/test-upstream-watch.mjs       # regression suite (offline, never notifies)
 ```
 
@@ -1118,7 +1118,7 @@ dsh plugin --profile web add C:\Users\User\Desktop\dsh-code-server-app
 ### Upgrading the VS Code tree (upstream = a code-server release)
 
 - **The version is decided at pack time**: `pnpm run vendor:latest` (= `--force`) pulls the tree of the npm **latest**
-  release; or use `pnpm run vendor:vscode -- --version 4.139.1` / `DSHCS_CODE_SERVER_VERSION`.
+  release; or use `pnpm run vendor:vscode -- --version 4.141.0` / `DSHCS_CODE_SERVER_VERSION`.
   With an existing `vendor/vscode`, a plain `pnpm pack` never upgrades (it is a no-op).
   **Source-tree precedence (fixed in 0.2.13)**: an explicit `--from` uses that tree, while an explicit
   `--force`/`--version` now **always goes to the registry** — before the fix a local source tree won
@@ -1147,7 +1147,7 @@ dsh plugin --profile web add C:\Users\User\Desktop\dsh-code-server-app
 - `productPath` (`<quality>-<commit>`, part of the client WebSocket path) is **computed from `lib/vscode/product.json`**,
   so upgrading the tree needs no code change — but the routes are registered at activation, so restart `dsh web` afterwards.
 - **No runtime auto-upgrade anymore**: nothing fetches latest at startup; the version is fully determined by the bundled artifact.
-- Bundled locally right now: the tree of `code-server@4.139.1` (VS Code 1.139.1, `productPath=stable-53c2f325…`).
+- Bundled locally right now: the tree of `code-server@4.141.0` (VS Code 1.141.0, `productPath=stable-8b41915d…`).
 
 ### Tree and install-location resolution
 

package/README.md

@@ -479,7 +479,7 @@ seq,并且 `/sync` 回应里带 `lastSeq`(高水位),扩展据此自查游标是
   (客户端半部与提问面板都是入库的手写源码 —— 整条链上**没有任何构建步骤**)。
 
 > 本机(BM: Windows 11 ARM64)实测:树/依赖全链路是"平台子包直挂插件依赖"供给 ——
-> 树包 `@jinsiyu/dshcs-vscode-server`(当前 4.139.1,44.4 MB tgz)、纯 JS 内部依赖与 7 个平台无关
+> 树包 `@jinsiyu/dshcs-vscode-server`(当前 4.141.0,tgz 约 44 MB)、纯 JS 内部依赖与 7 个平台无关
 > 重打包包直接进插件 `dependencies`、8 个平台专属重打包包按 win32-arm64/x64 进
 > `optionalDependencies`(包自带 os/cpu 自动选),原始名字由 `lib/native.js` 补 junction 还原
 > → healthz 200 → 停止 → 回收全链路验证。
@@ -535,7 +535,7 @@ pnpm run promote -- <version>
 | 目标 | 命令 |
 |---|---|
 | **打最新版(上游 code-server 发行版)** | `pnpm run vendor:latest`(= `--force`):从 registry 取 `code-server@latest` 的树到 `vendor/vscode`;之后**必须**重跑 `repack:build` 并重发全部子包 |
-| **指定版本** | `pnpm run vendor:vscode -- --version 4.139.1` |
+| **指定版本** | `pnpm run vendor:vscode -- --version 4.141.0` |
 | **从已装好的树快照** | `pnpm run vendor:vscode -- --from <code-server 目录>`(秒级) |
 | **开发期让树可直接跑** | `pnpm run vendor:vscode -- --dev-links`(额外把 `lib/vscode/node_modules` 用 junction 补上) |
 | **完整重打子包** | `pnpm run repack:build -- --target win32-arm64,win32-x64 --pack`(不给 `--from` 会自动 npm install 解包 + 编译,耗时)。`--target` 只决定**本次在这台机器上构建哪些目标**(原生包要现编,所以 Linux 目标在 Linux 机器或 `repacks.yml` 的 Linux 腿上构建);产品覆盖哪些目标、每模块在哪些目标上有子包,由 `scripts/repack-platforms.json` 决定 |
@@ -562,7 +562,7 @@ pnpm run watch:upstream                    # 同上,但会先过 pnpm 的依赖
 node scripts/watch-upstream.mjs --json     # 机器可读(DSH 会话内提醒解析这一份);人类输出转 stderr
 node scripts/watch-upstream.mjs --no-notify # 只报告、不发通知(回归 / 无人值守)
 node scripts/watch-upstream.mjs --fixture f.json # 用本地 JSON 当 registry 应答(离线)
-node scripts/watch-upstream.mjs --local 4.140.0  # 覆盖本地基线试算(不读 vendor/)
+node scripts/watch-upstream.mjs --local 4.141.0  # 覆盖本地基线试算(不读 vendor/)
 node scripts/test-upstream-watch.mjs       # 回归(离线、不发通知)
 ```
 
@@ -1056,7 +1056,7 @@ dsh plugin --profile web add C:\Users\User\Desktop\dsh-code-server-app
 ### 升级 VS Code 树(上游 = code-server 发行版)
 
 - **打包期决定版本**:`pnpm run vendor:latest`(= `--force`)取 npm **最新版 code-server** 的树并重建 `vendor/vscode`;
-  也可 `pnpm run vendor:vscode -- --version 4.139.1` 或设 `DSHCS_CODE_SERVER_VERSION`。
+  也可 `pnpm run vendor:vscode -- --version 4.141.0` 或设 `DSHCS_CODE_SERVER_VERSION`。
   已有 `vendor/vscode` 时,不带 `--force`/`--version` 不会升级(日常 `pnpm pack` 是 no-op)。
   **源树优先级(0.2.13 修正)**:显式 `--from` 用给定树;显式 `--force`/`--version` **一定走 registry**
   —— 修正前它们会被"本机已有源树"抢走(`defaultSourceTree()` 先命中 `vendor/code-server` 或 profile 里的旧树),
@@ -1081,7 +1081,7 @@ dsh plugin --profile web add C:\Users\User\Desktop\dsh-code-server-app
 - `productPath`(`<quality>-<commit>`,客户端 WS 路径的组成)**从 `lib/vscode/product.json` 现算**,
   升级树后无需改代码 —— 但也意味着切版本后必须重启 dsh web(路由在激活期注册)。
 - **不再有运行期自动升级**:不会在启动时联网取 latest;版本完全由内置产物决定。
-- 本机当前内置:`code-server@4.139.1` 的树(VS Code 1.139.1,`productPath=stable-53c2f325…`)。
+- 本机当前内置:`code-server@4.141.0` 的树(VS Code 1.141.0,`productPath=stable-8b41915d…`)。
 
 ### 树与安装位的解析路径
 

package/lib/vendored.json

@@ -100,7 +100,7 @@
     {
       "alias": "@vscode/windows-registry",
       "package": "@jinsiyu/dshcs-vscode-windows-registry",
-      "version": "1.2.0",
+      "version": "1.3.0",
       "platform": true,
       "targets": [
         "win32-x64",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-code-server-app",
-  "version": "0.3.71",
+  "version": "0.3.72",
   "description": "VS Code (from a code-server release) inside DSH: a right-sidebar tab driven by the plugin's own launcher over the in-process VS Code server (lib/launcher.mjs), plus an editor bridge (assets/extensions/dshcs-editor-bridge) that gives the agent what only the editor knows (unsaved buffers, language-server diagnostics, the active selection) and lets editor gestures drive the session. The bridge is completely read-only: all four of its routes (/health, /sync, /old, /event) are reads. Asking DSH from the editor opens a floating dialog inside the DSH page (draggable, resizable, bottom-right): the plugin's client half sends the question as user input (POST /api/code-server/ask/send) and renders that session's new content with DSH's own Markdown renderer - the same @deepseek-ai/dsh-client-ui-primitives instance the UI uses, required from the page's module table, so typography, highlighting and math match the interface and a renderer version mismatch is impossible. Thinking appears as collapsed rows and approval requests (writing outside the workspace / running commands) can be answered in place: whole-plugin write route POST /api/code-server/ask/approve, constrained to pending in-process requests and the outcomes allowed-once/rejected; dialog-first for 5 minutes, handed back to the official card the moment the dialog closes, never auto-approved. There is no build step anywhere: lib/client.js (client half including the dialog panel) and the extension are committed hand-written source, devDependencies holds a single test-only entry, and the published package carries no frontend bundle. Also: the tab claims DSH file addresses (dsh-resource://file/**) by file type (setting claimExtensions), so produced-file chips, delivered-file previews and inline prose mentions open in the workbench; the IDE is a resident surface moved with Element.moveBefore instead of being remounted, so switching sidebar tabs does not reload it; opening the tab switches the right sidebar to fullscreen by default (setting fullscreenOnOpen); a workspace switch re-navigates the workbench with the new ?folder= without restarting the IDE process. Requires a DSH with the right-sidebar services (sidebarRightTabs/sidebarRight, >= 0.1.5-alpha.1); older DSH versions only get an upgrade notice on the settings page. Two serving modes: loopback port (default) or same-origin mount on DSH's own webServer (/code-server, protected by ctx.connection.requestRejection). The diff the bridge opens always has the real pre-write text on the left, taken from result.value.before in tools/post-execute into a bounded snapshot cache and fetched by opaque key over the read-only GET /old, so files that are not open in the editor work too. No code-server Node layer, no argon2, no C++ toolchain.",
   "homepage": "https://github.com/jinsiyu/dsh-code-server-app",
   "repository": {
@@ -85,7 +85,7 @@
     "@jinsiyu/dshcs-ssh2": "1.17.0",
     "@jinsiyu/dshcs-vscode-fs-copyfile": "2.0.0",
     "@jinsiyu/dshcs-vscode-proxy-agent": "0.45.0",
-    "@jinsiyu/dshcs-vscode-server": "4.140.0",
+    "@jinsiyu/dshcs-vscode-server": "4.141.0",
     "@microsoft/1ds-core-js": "3.2.13",
     "@microsoft/1ds-post-js": "3.2.13",
     "@vscode/iconv-lite-umd": "0.7.1",
@@ -151,8 +151,8 @@
     "@jinsiyu/dshcs-vscode-windows-ca-certs-win32-x64": "0.3.4",
     "@jinsiyu/dshcs-vscode-windows-process-tree-win32-arm64": "0.8.0",
     "@jinsiyu/dshcs-vscode-windows-process-tree-win32-x64": "0.8.0",
-    "@jinsiyu/dshcs-vscode-windows-registry-win32-arm64": "1.2.0",
-    "@jinsiyu/dshcs-vscode-windows-registry-win32-x64": "1.2.0"
+    "@jinsiyu/dshcs-vscode-windows-registry-win32-arm64": "1.3.0",
+    "@jinsiyu/dshcs-vscode-windows-registry-win32-x64": "1.3.0"
   },
   "scripts": {
     "test": "node scripts/run-all-tests.mjs",

package/vendor/VENDOR.json

@@ -1,12 +1,12 @@
 {
-  "codeServerVersion": "4.140.0",
-  "vscodeVersion": "1.140.0",
-  "productPath": "stable-ccc19adc2e8992e18b14dd25eb1e646f5b9ef7cf",
+  "codeServerVersion": "4.141.0",
+  "vscodeVersion": "1.141.0",
+  "productPath": "stable-8b41915d25547e2edd553bab03ea4cbd621f98c5",
   "layout": "vscode-only",
-  "preparedAt": "2026-10-04T13:22:27.553Z",
+  "preparedAt": "2026-10-09T06:02:25.638Z",
   "source": "registry",
   "node": "v24.21.0",
   "platform": "linux",
   "arch": "x64",
-  "sizeMB": 165.1
+  "sizeMB": 165.9
 }