fix(main): resolve shell PATH not inherited in macOS GUI-launched app

[broediger]

Summary

• Fixes shell PATH not being inherited when the app is launched from Finder/Dock on macOS
• Reads the user's actual PATH from their login shell at app startup using execFileSync
• Uses unique delimiters (__PPTB_PATH_START__/__PPTB_PATH_END__) to safely extract PATH, ignoring any shell startup noise (banners, motd, debug echo in .zshrc/.bashrc)

Why not fix-path? The fix-path package (v4+) is ESM-only, which conflicts with the project's CommonJS main process. A dynamic import() would introduce a race condition before managers are instantiated. This inlines the same technique fix-path uses under the hood — without the dependency.

Closes #506

Test plan

• Run pnpm run build — verify no type/build errors
• Run pnpm run package:mac — package the app (unsigned with CSC_IDENTITY_AUTO_DISCOVERY=false)
• Open the .app from Finder (double-click, not from terminal)
• Enable debug mode, install a tool via npm — should succeed
• Verify terminal spawning and browser detection also work

[Copilot]

Pull request overview

Fixes missing shell PATH when the app is launched from Finder/Dock on macOS by patching process.env.PATH at startup using the user’s login shell output.

Changes:

• Runs a login/interactive shell at main-process startup and extracts PATH between unique delimiters.
• Updates process.env.PATH so spawned processes can locate npm/pnpm in GUI-launched sessions.

[Power-Maverick]

@broediger can you provide more information as we have few dev including myself that develop on mac and have never encountered any issues.

[broediger]

If you start the PowerPlatformToolBox from Dock or Finder, you can try to add a tool via Debug Session via registry install:
"Installation Failed
Failed to install pptb-xxx-yyy: Error invoking remote method 'install-tool': Error: No package manager found. Please install pnpm or npm globally: To install a package manager, choose one of the following: **Install pnpm"
As I've installed npm globally through nvm and my path is "~/.nvm/versions/node/v24.14.0/bin/npm." as I use that for my workflows.
My guess, either your pnpm /npm is installed in the default path "/usr/local/bin" or you starting the tool out of the terminal, where you get the PATH context out of the terminal.

[Power-Maverick]

Thank you. It is for the debug with npm package name scenario; got it. Will check with the team.

[Power-Maverick]

I am unable to reproduce the issue without this fix. @cyco77 can you check on your end if you are able to reproduce the issue without either a stable or insider version so that we can test the same scenario with this fix applied to verify it works

[cyco77]

same on my side... tried different thing but did not facing this issue

[broediger]

could you test this on your machine, that would check your local npm path:
env -i PATH="$(launchctl getenv PATH 2>/dev/null || echo /usr/bin:/bin:/usr/sbin:/sbin)"
/bin/sh -c 'command -v npm pnpm node || echo "NONE FOUND — reproduces the bug"'

[cyco77]

here is my output:
PATH=
/Users/lars.hildebrandt/.nvm/versions/node/v22.21.1/bin/npm
/Users/lars.hildebrandt/.nvm/versions/node/v22.21.1/bin/pnpm
/Users/lars.hildebrandt/.nvm/versions/node/v22.21.1/bin/node

[Power-Maverick]

Hey so the issue you tried to fix was not the correct one. There was an issue in the tool registry as well as how the package was getting installed (folder was not reading correctly) – which I have fixed in the upcoming release so closing this PR without a merge.