@stacksjs/defaults 0.72.101 → 0.72.103

package/ai/skills/stacks-desktop/SKILL.md

@@ -140,6 +140,11 @@ Keys the bundle must own — `CFBundleIdentifier`, `CFBundleExecutable`,
 `CFBundleVersion`, and the rest of the identity — are ignored with a note.
 Rewriting those produces a bundle that does not match what was signed.
 
+Inside the bundle the launcher is named after the app, not `stacks-desktop`.
+macOS names the *process* in every permission prompt, so a launcher keeping the
+framework's build name asks "stacks-desktop would like to access files in your
+Downloads folder" — which reads like something to refuse.
+
 Application data belongs in `~/Library/Application Support/<AppName>`, never
 inside the bundle — `/Applications` is not writable by the user, and the bundle
 is replaced wholesale on update.

package/ide/vscode/package.json

@@ -2,7 +2,7 @@
   "publisher": "Stacks",
   "name": "vscode-stacks",
   "displayName": "Stacks",
-  "version": "0.72.101",
+  "version": "0.72.103",
   "description": "A modern Stacks development environment.",
   "license": "MIT",
   "funding": "https://github.com/sponsors/chrisbbreuer",

package/package.json

@@ -2,7 +2,7 @@
   "name": "@stacksjs/defaults",
   "type": "module",
   "sideEffects": false,
-  "version": "0.72.101",
+  "version": "0.72.103",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/stacksjs/stacks.git",
@@ -51,7 +51,7 @@
   "dependencies": {
     "@iconify-json/f7": "^1.2.2",
     "@iconify-json/hugeicons": "^1.2.27",
-    "@stacksjs/mobile": "^0.72.101",
+    "@stacksjs/mobile": "^0.72.103",
     "@stacksjs/sanitizer": "^0.2.113"
   },
   "scripts": {

package/resources/components/Dashboard/UI/WindowControls.stx

@@ -11,7 +11,8 @@
   JavaScript or can flash.
 
   Use them for a frameless window, where the page really does own its chrome,
-  and for a web dashboard that wants the look of one.
+  and for a web dashboard that wants the look of one. In both the variable is
+  unset, and these are what the viewer sees.
 -->
 <script client>
 import { useWindowControls } from '../../../../functions/craft'

package/views/dashboard/layouts/default.stx

@@ -642,10 +642,11 @@ onDestroy(() => {
   >
     <template #header>
       <!-- Chrome strip. The traffic lights are the platform's, so this draws
-          none and reserves whatever room the host says they need: 62px in a
-          titlebarHidden window where they float over this sidebar, nothing in
-          a window that keeps them in a titlebar, and nothing in a browser,
-          which has no window buttons at all. It is also the window drag
+          none and reserves whatever room the host says they need. Craft
+          measures its own window: the far edge of the real buttons where they
+          float over this sidebar, and nothing where they do not: a window
+          that keeps them in a titlebar, a fullscreen one whose titlebar has
+          slid away, or a browser, which has no window buttons at all. It is also the window drag
           region, and in a browser it is the same empty strip macOS sidebars
           carry above their first row. -->
       <SidebarHeader windowControls="native" />