dsh-wsl-tool 1.8.2 → 1.9.0

package/PUBLISHING.md

@@ -61,10 +61,11 @@ both that the entry stays relative and that it resolves.
    ```
 
    `npm run sync` defaults to
-   `%USERPROFILE%/.dsh/profiles/web/node_modules/dsh-wsl` — the folder the
+   `%USERPROFILE%/.dsh/profiles/desktop/node_modules/dsh-wsl` — the folder the
    profile's dependency key created, which need not match the npm name. Pass a
    path to target another profile. Restart DSH afterwards: the plugin is imported
-   once at load.
+   once at load. A patch change (the tool row, or the sidebar terminal override)
+   is read at composition time, so it needs that restart too.
 
 3. The tag runs the pipeline. The order is deliberate — the release asset goes
    **first** because it is the market's critical path, then npm, so a failing npm
@@ -100,6 +101,14 @@ both that the entry stays relative and that it resolves.
    artifact, not just the metadata. Scripted requests to `npmjs.com`'s HTML hit a
    Cloudflare challenge; the registry API is the source of truth.
 
+   Expect the registry's caches to lag a publish by minutes, and to lag
+   *inconsistently*: the full packument, the abbreviated (install) packument,
+   `/-/package/<name>/dist-tags` and the tarball URL each cache separately, so one
+   endpoint can already report the new version while `npm install` still answers
+   `404` for its tarball. Re-query instead of concluding the publish failed, and
+   cache-bust the tarball URL (`?cb=<random>`) to tell a stale negative entry apart
+   from an artifact that is genuinely missing.
+
    **Market asset** (this is what users install, and it is independent of npm):
 
    ```sh

package/README.md

@@ -134,6 +134,44 @@ A background job is owned by the calling session (`owner: exec.agent.id`), which
 is what lets the model read it back with `job_output`/`job_kill` and what keeps
 other sessions out; an execution with no agent starts the job unowned.
 
+## A WSL terminal in the sidebar
+
+Installing this plugin also gives the desktop app's sidebar terminal a **WSL**
+shell. `cordis.patch.yml` overrides the composed `terminal-controller` row, whose
+configured shell is listed **first** and selected by default; the shells that row
+discovers (`powershell`, `cmd`, `bash`, …) stay selectable, so 新建终端 offers WSL
+next to them.
+
+```yaml
+- id: terminal-controller
+  config:
+    shell:
+      path: 'C:\Windows\System32\wsl.exe'
+      name: WSL
+      args: ['-e', 'bash', '-l']
+```
+
+- No distribution is pinned, so `wsl.exe` follows the system default — the same
+  rule the tools use when `DSH_WSL_DISTRO` is unset.
+- The session workspace is a Windows path that `wsl.exe` translates, so the
+  terminal opens in `/mnt/<drive>/…` exactly like the Windows shells do; and it is
+  a real PTY (`xterm-256color`), so full-screen programs work.
+- **Pinning a distribution, or choosing a different default, is a later patch
+  layer** — a profile's own `cordis.patch.yml` wins over this bundle:
+
+  ```yaml
+  - id: terminal-controller
+    config:
+      shell:
+        path: 'C:\Windows\System32\wsl.exe'
+        name: WSL
+        args: ['-d', 'Ubuntu-22.04', '-e', 'bash', '-l']
+  ```
+
+  An id-targeted patch replaces that row's whole config, so restate anything else
+  you had set on it.
+- Applies at the next app start.
+
 ## `wsl` parameters
 
 | Param | Required | Type | Notes |
@@ -342,7 +380,7 @@ A `file:` dependency is a **copy**, so editing this checkout does not change wha
 DSH loads. After any change:
 
 ```sh
-npm run sync                  # copies into ~/.dsh/profiles/web/node_modules/dsh-wsl
+npm run sync                  # copies into ~/.dsh/profiles/desktop/node_modules/dsh-wsl
 npm run sync -- /path/to/profiles/<profile>/node_modules/<your-key>
 ```
 

package/README.zh-CN.md

@@ -116,6 +116,39 @@ DSH_SUBPROCESS_LOCAL=/path/to/dsh/node_modules npm run test:real
 `job_output`/`job_kill` 读回它的依据，也是其他会话读不到它的围栏；exec 里没有 agent 时
 任务则是无主的。
 
+## 在侧边栏开一个 WSL 终端
+
+装了这个插件，桌面版侧边栏终端就多出一个 **WSL** shell：插件的 `cordis.patch.yml` 覆盖组合里的
+`terminal-controller` 行，而该行配置的 shell 会排在**第一位**并成为默认；它由 `shellCandidates`
+发现的 `powershell`/`cmd`/`bash` 等仍然可选，所以「新建终端」里 WSL 与它们并列。
+
+```yaml
+- id: terminal-controller
+  config:
+    shell:
+      path: 'C:\Windows\System32\wsl.exe'
+      name: WSL
+      args: ['-e', 'bash', '-l']
+```
+
+- **不锁定发行版**：`wsl.exe` 跟随系统默认，与工具在未设 `DSH_WSL_DISTRO` 时的规则一致。
+- 会话工作区是 Windows 路径，`wsl.exe` 会自动翻译，因此终端像 Windows shell 一样落在
+  `/mnt/<盘>/…`；而且是**真 PTY**（`xterm-256color`），全屏程序可用。
+- **要锁定发行版或换默认 shell**，在更靠后的 patch 层里重述该行即可 —— profile 自己的
+  `cordis.patch.yml` 优先于本组合包：
+
+  ```yaml
+  - id: terminal-controller
+    config:
+      shell:
+        path: 'C:\Windows\System32\wsl.exe'
+        name: WSL
+        args: ['-d', 'Ubuntu-22.04', '-e', 'bash', '-l']
+  ```
+
+  按 id 的 patch 会**整段替换**该行 config，其他设置要一并重述。
+- **下次启动应用时生效。**
+
 ## `wsl` 参数
 
 | 参数 | 必填 | 类型 | 说明 |
@@ -318,7 +351,7 @@ DSH_SUBPROCESS_LOCAL=/path/to/dsh/node_modules npm run test:real
 `file:` 依赖是**副本**，改本仓库不会改变 DSH 实际加载的内容。任何改动之后：
 
 ```sh
-npm run sync                  # 复制到 ~/.dsh/profiles/web/node_modules/dsh-wsl
+npm run sync                  # 复制到 ~/.dsh/profiles/desktop/node_modules/dsh-wsl
 npm run sync -- /path/to/profiles/<profile>/node_modules/<你的依赖名>
 ```
 

package/cordis.patch.yml

@@ -19,3 +19,35 @@
 - insert:
     - id: tool-wsl
       name: './index.js'
+
+# ── Sidebar terminal: a WSL shell, listed first and selected by default ────────
+#
+# The desktop app's 新建终端 list is built from the composed `terminal-controller`
+# row: it discovers shells from `shellCandidates` and puts the configured `shell`
+# first. Overriding that row here is what makes installing this plugin also give
+# you a Linux terminal in the sidebar. (A candidate entry cannot do it: a shell
+# discovered by name gets `-i` appended, and `wsl.exe -i` is a hard error.)
+#
+# The path is absolute because the configured shell must resolve, and a shell that
+# cannot resolve makes every new terminal fail rather than just this one: wsl.exe
+# ships with Windows at a fixed location, so this resolves even where no
+# distribution is installed yet.
+#
+# No distro is pinned, so `wsl.exe` follows the system default — the same rule the
+# tools use when DSH_WSL_DISTRO is unset. Add `-d <name>` to `args` to pin one.
+#
+# This changes the default terminal shell, which is deliberate for a WSL plugin
+# and reversible: a later patch layer wins, so restating the row in a profile's own
+# cordis.patch.yml overrides it (and a profile that sets its own `shell` there is
+# unaffected by this row).
+#
+# An id-targeted patch replaces the whole config, so anything the layer below set
+# on this row (limits, scrollback, a custom shellCandidates list) falls back to its
+# schema default. Only `shell` is set here on purpose. Never add `disabled:` here:
+# that would switch off the terminal feature for the user instead of just this row.
+- id: terminal-controller
+  config:
+    shell:
+      path: 'C:\Windows\System32\wsl.exe'
+      name: WSL
+      args: ['-e', 'bash', '-l']

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-wsl-tool",
-  "version": "1.8.2",
+  "version": "1.9.0",
   "description": "Run Linux commands from Windows through WSL, essentially matching a native Linux DSH for command execution: background jobs, stdin, path translation, a destructive-command guard and a WSL capability report. WSL calls run below the DSH sandbox, and a project on a Windows drive keeps Windows filesystem semantics.",
   "type": "module",
   "main": "index.js",