dsh-remote-vs 0.9.2 → 0.10.0

package/README.en.md

@@ -37,8 +37,9 @@ dsh plugin --profile web add dsh-remote-vs
 (From npm, recommended; installing straight from the repository also works:
 `dsh plugin --profile web add github:xiray-xia/dsh-remote-vs`.)
 
-Requires DSH `0.2.1-alpha.3` or newer (`engines.dsh` enforces the range; **the tested
-baseline is `0.2.1-rc.2`**). `--profile web` selects which profile to install into —
+Requires DSH `0.2.2-alpha.2` or newer (`engines.dsh` enforces the range; **the tested
+baseline is `0.2.2-alpha.2`**). Older Hosts (`0.2.1-rc.2` generation) need plugin `0.9.3`: the
+Remote preset of this version uses the `0.2.2-alpha.2` tool schema. `--profile web` selects which profile to install into —
 this is a Web plugin, so it has to go into the profile your Web GUI runs from (`web` is
 the common name; use your own profile's name).
 
@@ -205,6 +206,16 @@ Both surfaces share one state module (`store.tsx`): **the sidebar "Remote" page*
   hidden it does **no remote work** (directory listings, the SCM stash/branch/remote queries and editor
   image reads all wait for the next foreground pass), and visibility is MEASURED on the plugin root
   (IntersectionObserver) instead of being taken from a host prop.
+- **No blank wait when switching workspaces**: the last git state read for each (workspace, repository
+  directory) is kept in memory, so switching back paints the change list, branch and tree marks **in the
+  same frame** and re-reads behind it. The panel says "cached · refreshing" meanwhile; the change list and
+  the stage/commit/discard buttons still act on that workspace (⟳ and "reset repository directory" are
+  disabled while the background read runs — pressing them would only queue a second walk of the same tree).
+  One git read per repository DIRECTORY at a time (changing the directory lets the two directories' reads run
+  side by side — they are two different walks); a manual refresh's answer is always post-click (it queues
+  after the running read); a read of a workspace you left behind only fills its own cache and never repaints;
+  a failed background read keeps the list and shows why instead of declaring the workspace "not a
+  repository". The first visit to a workspace still waits — cache cannot invent a read.
 - **Editor**: tabs plus an info bar (path, language, **build stamp**, `tok N` coloured-token count,
   saved state, reload/save). Those three marks exist for troubleshooting: the stamp answers "is the
   browser running the bundle I just built?", `tok 0` answers "did a grammar match this extension?".
@@ -291,7 +302,7 @@ over helper RPC (fs) / ssh2 (processes), local stays untouched; both share one H
 
 - Alias dirs: `$DSH_HOME/remote-ssh/aliases/<id>` (empty shells, routing keys only), auto-registered into the native workspace list as `<server> > <base>`
 - Routing switch (dropdown at the top of Settings → Remote hosts; underneath it is profile patch `- id: remote-vs`, `config.routingMode`, volatile, no restart):
-  `off` (default, local passthrough) / `shadow` (logs, still local) / `enforce` (real routing)
+  default `enforce` (real routing); switch to `off` (pure local passthrough) / `shadow` (logs, still local) as debugging escapes
 - New workspace: the native "Add workspace…" entry is adopted (local/remote dual tab; remote leg = host→push→bind wizard)
 - Presets: a `Remote` preset (bash toolset); under enforce, new remote sessions switch to it automatically (default preset only, never overrides an explicit choice)
 - Ground truths (measured, not assumed):
@@ -309,7 +320,7 @@ over helper RPC (fs) / ssh2 (processes), local stays untouched; both share one H
 Upstream never published helper binaries (all Release assets are empty), so this plugin builds its own:
 
 - Build machine: WSL2 Ubuntu-22.04 (glibc 2.35, matching the remote targets), Node v24.21.0 + pnpm 11.28.5
-- Sources: the `dsh-v0.2.1-alpha.2` tag (the **build baseline**: what must match is the wire protocol version, not the Host version — it is still 2, so a Host upgrade to alpha.4 or alpha.5 does not require a rebuild)
+- Sources: the `dsh-v0.2.1-alpha.2` tag (the **build baseline**: what must match is the wire protocol version, not the Host version — our protocol is still **2**, so a Host upgrade to `0.2.2-alpha.2` needs no rebuild either: the plugin intentionally stays on `dsh-ssh@0.2.1-rc.2`, and the new generation's protocol 3 is deliberately not followed — see §2.26 of the maintenance notes)
 - Command: stock script `pnpm exec tsx scripts/build-exe-for-ssh-helper.ts --target=node24-linux-x64`
 - Only deviation: no docker for the manylinux 2.28 rebuild, so a `DSH_GLIBC_CEILING`
   env override was added (default stays 2.28); this build targets 2.35 (see `glibc-ceiling.patch` in the cache dir)

package/README.md

@@ -34,7 +34,8 @@ dsh plugin --profile web add dsh-remote-vs
 
 （从 npm 装，推荐；也可以直接跟仓库装：`dsh plugin --profile web add github:xiray-xia/dsh-remote-vs`。）
 
-要求 DSH `0.2.1-alpha.3` 及以上（`engines.dsh` 门到底；**当前实测基线 `0.2.1-rc.2`**）。
+要求 DSH `0.2.2-alpha.2` 及以上（`engines.dsh` 门到底；**当前实测基线 `0.2.2-alpha.2`**）。
+旧 Host（`0.2.1-rc.2` 一代）请用插件 `0.9.3`：新版的 Remote 预设用了 `0.2.2-alpha.2` 的工具 schema。
 `--profile web` 指明装进哪个 profile —— 本插件是 Web 插件，
 必须装进 Web GUI 所用的那个（`web` 是常见命名，以你自己的 profile 名为准）。
 
@@ -193,6 +194,13 @@ dsh_remote_vs/
   保持挂载，切回来不重新拉取、不闪。隐藏期间**不做远端工作**（目录列表、SCM 的 stash/分支/远程查询、
   编辑器图片读取都等回到前台再补一次），可见性是对插件根节点实测的（IntersectionObserver），
   不靠宿主传参。
+- **切工作区不空白**：每个（工作区, 仓库目录）最近一次读到的 git 状态留在内存里，切回时**同一帧**画出
+  更改列表、分支和文件树上的状态标记，再在后台重读替换；期间面板标「缓存 · 后台刷新中」，更改列表与
+  暂存/提交/丢弃等按钮照常作用于该工作区（⟳ 与「重置仓库目录」在后台读期间置灰 —— 再点只会对同一棵树
+  重复排队）。同一**仓库目录**同时最多一条 git 读（换目录时新旧目录的读会并行，它们本来就是两个目录）；
+  手动刷新的结果一定晚于点击（排在后台读之后取最新结果），切走的读只写自己那份缓存、绝不上屏；后台读
+  失败保留原列表并显示原因，不会把工作区误判成"没有仓库"。刷新浏览器/重启 Host 后第一次切换仍要等
+  一次，这是有意的。
 - **编辑器**：多标签 + 信息栏（路径、语言、**构建戳**、`tok N` 着色 token 数、已保存状态、重载/保存）。
   信息栏三个标记是给排障用的：构建戳判定"浏览器跑的是不是刚编的包"，`tok 0` 判定语法包是否命中。
 - **悬浮编辑器**：文件树 / 搜索结果 / 源代码管理右键「在悬浮编辑器中打开」，或双击「远程编辑器」标签，
@@ -259,7 +267,7 @@ helper RPC（fs）/ ssh2（进程），本地一切不变；两者同 Host、共
 
 - 别名目录：`$DSH_HOME/remote-ssh/aliases/<id>`（空壳，只做路由键），自动注册进原生工作区列表，标题 `<server> > <base>`
 - 路由开关（设置 → 远程主机页顶部下拉；底层是 profile patch `- id: remote-vs` 下 `config.routingMode`，volatile，免重启）：
-  `off`（默认，直通本地）/ `shadow`（记日志仍走本地）/ `enforce`（真路由）
+  默认 `enforce`（真路由）；可切 `off`（纯直通本地）/ `shadow`（记日志仍走本地）作为排障开关
 - 新建工作区：原生"添加工作区…"入口已接管（本地/远端双 tab；远端腿=主机→推送→绑定向导）
 - 预设：`Remote` 预设（bash 工具集）；enforce 下远端新会话自动切过去（默认预设才切，不践踏显式选择）
 - 顶层真相（实测结论，非假设）：
@@ -277,7 +285,9 @@ helper RPC（fs）/ ssh2（进程），本地一切不变；两者同 Host、共
 官方从未发布 helper 二进制（Release assets 全空），本插件走自编译：
 
 - 构建机：WSL2 Ubuntu-22.04（glibc 2.35，与目标远端一致），Node v24.21.0 + pnpm 11.28.5
-- 源码：`dsh-v0.2.1-alpha.2` tag（**构建基线**：对齐的是 wire 协议号，不是 Host 版本号 —— 协议号至今仍是 2，故 Host 升到 alpha.4 / alpha.5 都无需重编）
+- 源码：`dsh-v0.2.1-alpha.2` tag（**构建基线**：对齐的是 wire 协议号，不是 Host 版本号 —— 我们用到的
+  协议号仍是 **2**，Host 升到 `0.2.2-alpha.2` 也不需要重编：插件自行停在 `dsh-ssh@0.2.1-rc.2`，
+  新 Host 那一代 `dsh-ssh` 的协议 3 我们故意不跟，差异见维护文档 §2.26）
 - 命令：官方原脚本 `pnpm exec tsx scripts/build-exe-for-ssh-helper.ts --target=node24-linux-x64`
 - 唯一偏离：无 docker 跑不了 manylinux 2.28 重编，加了 `DSH_GLIBC_CEILING`
   环境覆盖（默认仍 2.28），本次以 2.35 构建（见缓存目录 `glibc-ceiling.patch`）

package/cordis.patch.yml

@@ -54,7 +54,7 @@
       inject: [localFileReferences, remoteWorlds]
 
     # Remote agent preset, bound to this bundle's lifecycle.
-    # Mirrored from preset-standard @ dsh 0.2.1-alpha.3 with these diffs:
+    # Mirrored from preset-standard @ dsh 0.2.2-alpha.2 with these diffs:
     #   1. persona prefix reframed for remote SSH work (transparent routing);
     #   2. tool-bash moved into an isolated shell group with our routed bash
     #      executor (stock root shell stays pwsh on Windows);
@@ -67,6 +67,12 @@
     # preset) right after `tool-plugin-manager` — mirrored here for the same
     # reason as above: a row missing from the mirror is a preset that silently
     # loads a different toolset than stock.
+    # 0.2.2-alpha.2 note: stock dropped `tool-subagent-list-agents` (the
+    # `dsh-tool-subagent-control/list-agents` subpath is gone from the package),
+    # renamed `modelSelectionSettings` to `modelSelection` + `modelDiscovery`,
+    # and made the plugin-manager row conditional on `profileContext`. All
+    # three are mirrored here: the first one is a hard module-resolution error,
+    # the other two are schema drift.
     - id: preset-remote
       name: '@deepseek-ai/dsh-agent-preset'
       config:
@@ -207,14 +213,13 @@
             config:
               - id: tool-subagent-control
                 name: '@deepseek-ai/dsh-tool-subagent-control'
-              - id: tool-subagent-list-agents
-                name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
               - id: tool-subagent
                 name: '@deepseek-ai/dsh-tool-subagent'
                 config:
                   provider: spawn
                   toolName: subagent
-                  modelSelectionSettings: true
+                  modelSelection: true
+                  modelDiscovery: true
               - id: tool-subagent-fork
                 name: '@deepseek-ai/dsh-tool-subagent'
                 config:
@@ -241,7 +246,7 @@
             name: '@deepseek-ai/dsh-tool-present'
           - id: tool-plugin-manager
             name: '@deepseek-ai/dsh-plugin-manager/tools'
-            disabled: true
+            disabled: !!js "!ctx.get('profileContext')"
           - id: tool-plugin-market
             name: '@deepseek-ai/dsh-plugin-market/tools'
             disabled: true