CLI socket (diffusion-studio.sock) never created; every dapi command fails with 'not running' even though the app IS running and a project is open

[yoavxyoav]

Reproduced on a completely clean install via the official Homebrew cask (brew install --cask diffusionstudio/tap/editor), version 0.204.1, on macOS (Apple Silicon).

Steps:

1. Fresh install via brew cask (previously also tried a manual .dmg install with the same result).
2. Launched the app, signed in (existing account, Free Plan).
3. Confirmed the app process is running and holds its own SingletonSocket lock file.
4. Opened a real project (an existing project auto-reopened on launch: 'Wild Ocean 5 Sep', with a scene visible in the editor).
5. Ran 'dapi context', 'dapi whoami', 'dapi logs' -- all fail identically with: 'Diffusion Studio is not running. Launch the app first, then retry.'
6. Inspected dapi's own source: it expects a Unix socket at $TMPDIR/diffusion-studio.sock (os.tmpdir() in Node). Confirmed via lsof that the running app process never creates this file -- only its own internal SingletonSocket lock exists, never diffusion-studio.sock.
7. Tried: restarting the app, reinstalling via the official brew cask from scratch, running dapi from a shell with a corrected $TMPDIR matching the real macOS per-user temp dir, and using the app's own 'Install dapi Command Line Tool...' menu item (installs the CLI symlink but does not appear to affect the runtime socket).

Expected: dapi should be able to connect to a running instance with an open project.
Actual: every dapi command fails immediately as if the app were not running at all, even though it demonstrably is.

Repro

dapi context
dapi whoami
dapi open <project-path>

Environment

dapi	0.204.1
platform	darwin 24.6.0 (arm64)
node	v24.18.0
app	not running