Fix: npm run build:apps path resolution for paths with spaces

[CookieDarb]

What?

Closes #738

Fixes the bug where npm run build:apps (and npm run build) fails with ENOENT when the repository is located in a directory path containing spaces.

Why?

bin/build-apps.mjs previously resolved the project root directory using new URL( '..', import.meta.url ).pathname, which resolved spaces to %20, causing readdirSync to receive an invalid filesystem path and build failed with ENOENT: no such file or directory.

How?

• bin/build-apps.mjs:
  • Used fileURLToPath from node:url to correctly resolve and decode the native filesystem path for the project root.
  • Added an existsSync( appsDir ) guard matching vite.config.js to safely exit with code 0 if no apps directory exists.

Testing Instructions

1. Place or clone the plugin in a directory path with spaces (e.g. Local Sites/ or /tmp/test space/desktop-mode).
2. Run npm run build:apps or npm run build.
3. Verify that all apps (code-blue, my-wordpress, os-settings, trash) compile successfully into assets/js/apps/ with exit code 0.

Use of AI Tools

AI assistance: Yes
Tool(s): Antigravity
Model(s): Gemini
Used for: Investigating the build error and suggesting changes. Final decisions and edits were made by me.

[AllTerrainDeveloper]

Thanks! LGTM!