ph-desktop-shell

The Powerhouse desktop shell: a Tauri app that supervises a Powerhouse project's stack (ph run desktop, uniform-runners) and windows Connect once the stack answers. One Cargo workspace, two crates:

• crates/ph-desktop-shell — the shell as a LIBRARY: supervision, the bundled-stack (resources/stack + shell.json) packaged-app path, readiness probe, tray, .phd launch queue, diagnostics log. No identity.
• apps/powerhouse-desktop — the Powerhouse-identity app: a three-line main.rs plus tauri.conf.json (productName, identifier, icons, file associations). Every builder shell generated by ph generate desktop-shell has exactly this shape with the builder's own identity.

Build

Before pushing, run the CI gate locally — ci.yml runs exactly this script, so green here means green there:

node scripts/check.mjs

node scripts/fetch-node.mjs apps/powerhouse-desktop   # sidecar node, once
cargo build -p powerhouse-desktop                     # debug exe
cargo tauri build                                     # NSIS installer (in apps/powerhouse-desktop)

The webview opens ui/index.html (a loading page) and navigates to the supervised stack's Connect once its port answers. Mode resolution: PH_RUN_* env (dev flows, wired by @powerhousedao/desktop's runner) → bundled resources/stack (the packaged app) → legacy sidecar if present → a logged "nothing to supervise".

Diagnostics land in the app log dir (ph-win.log); PH_WIN_DEVTOOLS=1 opens the webview devtools at startup.