dsh-plugin-wsl-env 0.1.9 → 0.1.10

package/CHANGELOG.md

@@ -12,6 +12,24 @@ reference below points at that record's numbering.
 
 ## [Unreleased]
 
+## [0.1.10] - 2026-10-02
+
+Metadata and one documentation addition. No behaviour change.
+
+### Changed
+
+- The package description now covers all four capabilities — commands, the file tools,
+  the folder picker, the GUI terminal — and the confinement, instead of naming only two
+  of them. It is the line npm shows under the package name in search results.
+
+### Documentation
+
+- The error table in `docs/ARCHITECTURE.md` states exactly what the model sees on a
+  filesystem denial: the denial marker and the escalation hint, line for line. It also
+  records why that makes `FS_OUTSIDE_DISTRO` worth its own code — a code the tool layer
+  does not decorate with those lines.
+
+
 ## [0.1.9] - 2026-10-02
 
 The last test gap from the closure review: the documented opt-out. No runtime change.

package/docs/ARCHITECTURE.md

@@ -189,6 +189,14 @@ to be invisible:
 | the distro is missing, stopped or unregistered | a `Wsl/Service/WSL_E_*` code on **stdout**, UTF-16 on some builds, with an empty stderr and exit 255 | `WslShellExecutor` reads the code with the NULs stripped and fails with the distro name and the remedy. Deliberately not a sandbox code: a wider permission cannot create a distro |
 | the working directory cannot be entered | a relay line on stderr, exit **0**, and the command runs in `/` | `WslShellExecutor` fails with the directory and the fallback, instead of reporting a success that acted on the wrong tree |
 
+
+What the model actually sees on a filesystem denial is two lines the tool layer
+prepends: `[sandbox: file access denied under <mode> mode]`, then
+`[sandbox: escalation available — retry this exact operation once with
+sandbox_permissions (the narrowest wider mode that suffices) + justification; the
+approval prompt asks the user]`. A code that is not `FS_SANDBOX_DENIED` gets neither
+line — which is the reason `FS_OUTSIDE_DISTRO` has its own code.
+
 ## The runtime mirror
 
 The checkout lives inside the distro. A DSH profile can only link a Windows path,

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-plugin-wsl-env",
-  "version": "0.1.9",
-  "description": "Run a DeepSeek Harness session against a WSL distro: a ctx.shell executor that runs commands inside the distro and a ctx.fs backend over its UNC share",
+  "version": "0.1.10",
+  "description": "Run a DeepSeek Harness session against a WSL distro: commands and the model's file tools run inside it, the folder picker and the GUI terminal open there, and commands are confined by bubblewrap inside the distro",
   "keywords": [
     "deepseek-harness",
     "dsh",