@aryacode/dsh-aryacode-polish 0.6.0 → 0.6.2

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog
 
+## [0.6.2] - 2026-10-28
+
+### Fixed
+
+- **The "+" menu and the GitHub dialog are opaque again in the desktop app.**
+  Both are portaled to `document.body`, which puts them outside the themed tree,
+  and they painted themselves with the harness menu fill `--dsw-specific-menu`
+  (`#f8f9fa94`, 58% alpha) relying on `backdrop-filter` to make that read solid.
+  The AryaCode desktop build does not composite that blur, so the page showed
+  through the panel. Every portaled surface now lays that fill over an opaque
+  `Canvas` base and keeps the blur only where the platform honours it.
+
+## [0.6.1] - 2026-10-28
+
+### Fixed
+
+- **"On this PC" opens the real Windows folder dialog in the desktop app again.**
+  The desktop preload exposes the OS chooser as `__DSH_DIRECTORY_PICKER__.pick()`
+  — the same bridge the shipped native picker uses — and the flow now calls it
+  directly, so picking a folder behaves exactly like the picker it stands in for.
+  The in-app folder list is now only the browser fallback, where no such bridge
+  exists and the composed picker's `pick` would wait on a dialog that cannot open.
+
 ## [0.6.0] - 2026-10-28
 
 ### Changed

package/client/face.js

@@ -252,6 +252,24 @@ const PILL_STYLE = {
 /** The label half of the pill, cut with an ellipsis rather than wrapped. */
 const PILL_LABEL_STYLE = { minWidth: 0, overflow: 'hidden', textOverflow: 'ellipsis', whiteSpace: 'nowrap' }
 
+/**
+ * The menu skin of the harness, made opaque on purpose.
+ *
+ * `--dsw-specific-menu` is a translucent fill (`#f8f9fa94`) that only reads as a
+ * solid surface because the harness pairs it with `backdrop-filter`. A plugin
+ * face has to portal its panels to `document.body`, and in the AryaCode desktop
+ * build that blur does not composite: the panel then showed the page behind it
+ * through a 58% fill. So the token stays as a tint over an opaque backdrop
+ * colour, and the blur is kept only where the platform actually honours it.
+ */
+const PANEL_SURFACE = {
+  backgroundColor: 'Canvas',
+  backgroundImage:
+    'linear-gradient(var(--dsw-specific-menu, rgba(248, 249, 250, 0.94)), var(--dsw-specific-menu, rgba(248, 249, 250, 0.94)))',
+  backdropFilter: 'var(--dsw-menu-backdrop-filter, none)',
+  border: '0.5px solid var(--dsw-alias-border-l2, rgba(0, 0, 0, 0.12))',
+}
+
 /** The dialog surface, copied from the harness `stat-dialog.module.css` skin. */
 const PANEL_STYLE = {
   position: 'fixed',
@@ -261,10 +279,8 @@ const PANEL_STYLE = {
   minWidth: 'min(300px, calc(100vw - 24px))',
   maxWidth: 'min(440px, calc(100vw - 24px))',
   padding: '16px',
-  border: 0,
   borderRadius: 'var(--dsw-radius-lg, 12px)',
-  background: 'var(--dsw-specific-menu, Canvas)',
-  backdropFilter: 'var(--dsw-menu-backdrop-filter, none)',
+  ...PANEL_SURFACE,
   boxShadow: 'var(--dsw-elevation-prominent, 0 10px 30px rgba(0, 0, 0, 0.18))',
   fontSize: '12px',
   lineHeight: '18px',
@@ -1064,16 +1080,33 @@ function WorkspaceSourceFlow(props) {
   }
 
   /**
-   * Start the folder browser at the machine's roots.
+   * Hand folder choice to the Host.
    *
-   * This deliberately does not call the Host's directory picker: a composed
-   * picker serves either `browse` or `native`, never both, and the browser build
-   * composes the one whose chooser cannot open there — a `pick` call would wait
-   * for a dialog that never appears. Our own listing behaves the same in the app
-   * and in the browser, and hands the chosen path back through `onPicked`.
+   * In the desktop app the preload exposes the real OS chooser as
+   * `__DSH_DIRECTORY_PICKER__.pick()` — the same bridge the shipped native
+   * picker uses — so the flow opens the Windows folder dialog and behaves like
+   * the stock picker it stands in for. In a browser there is no such bridge, and
+   * the composed picker's `pick` waits on a dialog that cannot open, so the flow
+   * lists folders itself instead of hanging.
    */
   const chooseOnPc = () => {
     if (busy) return
+    const bridge = typeof globalThis === 'undefined' ? undefined : globalThis.__DSH_DIRECTORY_PICKER__
+    if (bridge !== undefined && typeof bridge.pick === 'function') {
+      setBusy(true)
+      setError('')
+      Promise.resolve()
+        .then(() => bridge.pick())
+        .then(path => {
+          if (typeof path === 'string' && path !== '') {
+            land(path)
+            return
+          }
+          setBusy(false)
+        })
+        .catch(reason => fail(messageOf(reason)))
+      return
+    }
     setBusy(true)
     setError('')
     Promise.resolve()
@@ -1189,7 +1222,7 @@ function WorkspaceSourceFlow(props) {
         padding: '6px',
         overflowY: 'auto',
         borderRadius: 'var(--dsw-radius-lg, 12px)',
-        background: 'var(--dsw-specific-menu, Canvas)',
+        ...PANEL_SURFACE,
         boxShadow: 'var(--dsw-elevation-prominent, 0 8px 24px rgba(0,0,0,0.18))',
         fontSize: '12px',
         lineHeight: '18px',

package/docs/github-workspaces.md

@@ -38,7 +38,11 @@ The "+" menu's **Add workspace…** entry only appears when something occupies
 takes it stands in for the folder picker. This bundle takes it and offers the
 two sources the owner asked for:
 
-- **On this PC** — a folder browser driven by this bundle's own route
+- **On this PC** — the OS folder dialog. The desktop preload exposes it as
+  `window.__DSH_DIRECTORY_PICKER__.pick()`, the same bridge the shipped native
+  picker uses, so the flow calls it directly and behaves exactly like the picker
+  it stands in for. Where that bridge is absent (the web build) the flow falls
+  back to a folder browser driven by this bundle's own route
   (`api/polish.folders`, actions `roots` and `ls`): roots, a `..` row for going
   back, directories only, hidden and system entries filtered out, and **Use this
   folder** hands the current path to the flow's `onPicked`.
@@ -46,15 +50,14 @@ two sources the owner asked for:
   flow, so a finished clone hands its path back through the flow's `onPicked`,
   and the Shell creates the workspace exactly as it does for a picked folder.
 
-### Why the browser does not borrow the Host's chooser
+### Why the fallback exists at all
 
 A composed directory picker serves exactly one capability: `browse` answers
 `list` and `createDirectory`, `native` answers `pick`. The web profile composes
 the picker whose chooser cannot open there, so `directoryPicker.pick()` waits on
-a dialog that never appears — the first build of this flow did exactly that and
-the row spun forever. Owning the listing keeps one behaviour in the app and in
-the browser, needs no capability guess, and does not break when a profile mounts
-a different picker.
+a dialog that never appears — an earlier build of this flow did exactly that and
+the row spun forever. The preload bridge is the reliable door in the app; the
+listing is what a browser gets instead of a spinner.
 
 The tray of the foot keeps the sign-in state (`GitHub · <login>`, or
 `GitHub · signed out`) next to the balance, so the account is visible without

package/lib/client.js

@@ -41,7 +41,7 @@ window.__ModuleLoader__.load({
     ]
     const ROW_ID = "polish"
     const ROW_KEY = "@aryacode/dsh-aryacode-polish" + '#' + ROW_ID
-    const CLIENT_VERSION = "0.6.0"
+    const CLIENT_VERSION = "0.6.2"
 
     /**
      * The two pure decisions behind the balance line: which wallet to show, and how
@@ -419,6 +419,24 @@ window.__ModuleLoader__.load({
     /** The label half of the pill, cut with an ellipsis rather than wrapped. */
     const PILL_LABEL_STYLE = { minWidth: 0, overflow: 'hidden', textOverflow: 'ellipsis', whiteSpace: 'nowrap' }
 
+    /**
+     * The menu skin of the harness, made opaque on purpose.
+     *
+     * `--dsw-specific-menu` is a translucent fill (`#f8f9fa94`) that only reads as a
+     * solid surface because the harness pairs it with `backdrop-filter`. A plugin
+     * face has to portal its panels to `document.body`, and in the AryaCode desktop
+     * build that blur does not composite: the panel then showed the page behind it
+     * through a 58% fill. So the token stays as a tint over an opaque backdrop
+     * colour, and the blur is kept only where the platform actually honours it.
+     */
+    const PANEL_SURFACE = {
+      backgroundColor: 'Canvas',
+      backgroundImage:
+        'linear-gradient(var(--dsw-specific-menu, rgba(248, 249, 250, 0.94)), var(--dsw-specific-menu, rgba(248, 249, 250, 0.94)))',
+      backdropFilter: 'var(--dsw-menu-backdrop-filter, none)',
+      border: '0.5px solid var(--dsw-alias-border-l2, rgba(0, 0, 0, 0.12))',
+    }
+
     /** The dialog surface, copied from the harness `stat-dialog.module.css` skin. */
     const PANEL_STYLE = {
       position: 'fixed',
@@ -428,10 +446,8 @@ window.__ModuleLoader__.load({
       minWidth: 'min(300px, calc(100vw - 24px))',
       maxWidth: 'min(440px, calc(100vw - 24px))',
       padding: '16px',
-      border: 0,
       borderRadius: 'var(--dsw-radius-lg, 12px)',
-      background: 'var(--dsw-specific-menu, Canvas)',
-      backdropFilter: 'var(--dsw-menu-backdrop-filter, none)',
+      ...PANEL_SURFACE,
       boxShadow: 'var(--dsw-elevation-prominent, 0 10px 30px rgba(0, 0, 0, 0.18))',
       fontSize: '12px',
       lineHeight: '18px',
@@ -1231,16 +1247,33 @@ window.__ModuleLoader__.load({
       }
 
       /**
-       * Start the folder browser at the machine's roots.
+       * Hand folder choice to the Host.
        *
-       * This deliberately does not call the Host's directory picker: a composed
-       * picker serves either `browse` or `native`, never both, and the browser build
-       * composes the one whose chooser cannot open there — a `pick` call would wait
-       * for a dialog that never appears. Our own listing behaves the same in the app
-       * and in the browser, and hands the chosen path back through `onPicked`.
+       * In the desktop app the preload exposes the real OS chooser as
+       * `__DSH_DIRECTORY_PICKER__.pick()` — the same bridge the shipped native
+       * picker uses — so the flow opens the Windows folder dialog and behaves like
+       * the stock picker it stands in for. In a browser there is no such bridge, and
+       * the composed picker's `pick` waits on a dialog that cannot open, so the flow
+       * lists folders itself instead of hanging.
        */
       const chooseOnPc = () => {
         if (busy) return
+        const bridge = typeof globalThis === 'undefined' ? undefined : globalThis.__DSH_DIRECTORY_PICKER__
+        if (bridge !== undefined && typeof bridge.pick === 'function') {
+          setBusy(true)
+          setError('')
+          Promise.resolve()
+            .then(() => bridge.pick())
+            .then(path => {
+              if (typeof path === 'string' && path !== '') {
+                land(path)
+                return
+              }
+              setBusy(false)
+            })
+            .catch(reason => fail(messageOf(reason)))
+          return
+        }
         setBusy(true)
         setError('')
         Promise.resolve()
@@ -1356,7 +1389,7 @@ window.__ModuleLoader__.load({
             padding: '6px',
             overflowY: 'auto',
             borderRadius: 'var(--dsw-radius-lg, 12px)',
-            background: 'var(--dsw-specific-menu, Canvas)',
+            ...PANEL_SURFACE,
             boxShadow: 'var(--dsw-elevation-prominent, 0 8px 24px rgba(0,0,0,0.18))',
             fontSize: '12px',
             lineHeight: '18px',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aryacode/dsh-aryacode-polish",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "AryaCode Polish: one install for the small things that make AryaCode feel finished. One Plugins row, one switch per quality-of-life feature.",
   "keywords": [
     "dsh",