dsh-wsl-tool 1.10.3 → 1.10.4

package/lib/client.js

@@ -191,7 +191,12 @@ window.__ModuleLoader__.load({
         if (cursor === null || typeof cursor !== 'object') return undefined
         cursor = cursor[step]
       }
-      return cursor
+      // A `.volatile()` field can arrive as a cosmokit cell rather than its value;
+      // the platform's own form model hands out plain values, but unwrapping here
+      // costs nothing and keeps a switch from rendering a cell object as "on".
+      return cursor !== null && typeof cursor === 'object' && typeof cursor.get === 'function'
+        ? cursor.get()
+        : cursor
     }
 
     /**

package/lib/config.js

@@ -92,7 +92,25 @@ function envInt(env, name, fallback, min, max) {
 
 /** A configured boolean, or the fallback when the layer did not set one. */
 function setting(value, fallback) {
-  return typeof value === 'boolean' ? value : fallback
+  const raw = unbox(value)
+  return typeof raw === 'boolean' ? raw : fallback
+}
+
+/**
+ * Read one configuration value, unwrapping a volatile cell.
+ *
+ * A `.volatile()` schema field does NOT resolve to its value: schemastery wraps it
+ * with cosmokit's `createVolatile(default)`, which is why the shipped plugins read
+ * theirs as `config.timeoutMs.get()` (`dsh-bash-local`). The cell is written in
+ * place when the user edits the field, and that in-place write is exactly what makes
+ * an edit apply without remounting the plugin — so reading through `.get()` is both
+ * required for correctness and how live updates arrive. A plain value (an older
+ * host, or a hand-built settings object in a test) passes through untouched.
+ */
+function unbox(value) {
+  return value !== null && typeof value === 'object' && typeof value.get === 'function'
+    ? value.get()
+    : value
 }
 
 /**
@@ -101,7 +119,8 @@ function setting(value, fallback) {
  * @returns a distribution name to pin, or null to use the system default.
  */
 function resolveDistro(env, configured) {
-  if (typeof configured === 'string' && configured.trim() !== '') return configured.trim()
+  const distro = unbox(configured)
+  if (typeof distro === 'string' && distro.trim() !== '') return distro.trim()
   const raw = env.DSH_WSL_DISTRO
   return typeof raw === 'string' && raw.trim() !== '' ? raw.trim() : null
 }
@@ -121,7 +140,7 @@ function resolveWorkdir(env, settings) {
   // Only the ON position is authoritative: off means "whatever the layers below
   // say", so `DSH_WSL_WORKDIR=session` keeps working for a user who never opened
   // the panel, and a fresh install still starts in `~`.
-  if (settings.startInSessionWorkspace === true) return null
+  if (unbox(settings.startInSessionWorkspace) === true) return null
   const raw = env.DSH_WSL_WORKDIR
   if (typeof raw !== 'string' || raw.trim() === '') return DEFAULTS.workdir
   const value = raw.trim()
@@ -148,11 +167,12 @@ export function resolveConfig(env = process.env, settings = {}) {
   const maxCommandTimeoutMs = envInt(
     env, 'DSH_WSL_MAX_TIMEOUT_MS', DEFAULTS.maxCommandTimeoutMs, TIMEOUT_MS_MIN, DEFAULTS.maxTimerDelayMs,
   )
-  const tools = settings.tools ?? {}
+  const tools = unbox(settings.tools) ?? {}
   // 0 means "not configured", so the environment and the built-in default still
   // decide; a positive value is the user's own deadline.
-  const configuredTimeoutMs = Number.isInteger(settings.timeoutMs) && settings.timeoutMs > 0
-    ? settings.timeoutMs
+  const configuredTimeout = unbox(settings.timeoutMs)
+  const configuredTimeoutMs = Number.isInteger(configuredTimeout) && configuredTimeout > 0
+    ? configuredTimeout
     : undefined
   return {
     ...DEFAULTS,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-wsl-tool",
-  "version": "1.10.3",
+  "version": "1.10.4",
   "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. A left-sidebar panel switches each capability on or off, each with a one-line explanation, and an opt-in patch gives the desktop app's sidebar terminal a WSL shell. WSL calls run below the DSH sandbox, and a project on a Windows drive keeps Windows filesystem semantics.",
   "type": "module",
   "main": "index.js",