server-studio 1.1.0 → 1.1.1

package/README.md

@@ -206,9 +206,13 @@ Opening a terminal window is tested for real too, not just in theory: CI calls i
 command actually ran in the right folder. Linux gets a desktop from Xvfb with xterm, Windows runs it
 directly, and macOS is verified by hand since its runners have no scriptable Terminal.
 
-The one thing left uncovered is the native folder picker, because a modal dialog cannot be
-automated. Its fallback is tested, so a machine with no dialog available reports cancelled rather
-than hanging, but the dialog itself has only been opened by hand on macOS.
+The **Browse** button opens a native dialog, so CI opens it for real on all three platforms and
+cancels it, checking the app gets a clean cancel rather than hanging. A machine with no picker
+installed is covered too, and reports cancelled instead of erroring.
+
+The one step no machine can do is click a folder and confirm, so the path that returns a chosen
+directory is exercised by hand rather than by CI. If Browse ever misbehaves on your system, type the
+path into the field instead. Nothing else depends on it.
 
 ## Your data
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "server-studio",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "A tiny dashboard for your local dev servers. One click to run, stop and open them, with one permanent port per project.",
   "author": "Md Mahdi Hasan",
   "license": "MIT",
@@ -20,7 +20,8 @@
     "prepack": "node scripts/build-plugin.js",
     "test": "node scripts/test.js",
     "test:terminal": "node scripts/test-terminal.js",
-    "postinstall": "node scripts/postinstall.js"
+    "postinstall": "node scripts/postinstall.js",
+    "test:picker": "node scripts/test-picker.js"
   },
   "files": [
     "bin",