dfb76d36d5
Desktop launch and the update-chain rebuild install npm deps whose child scripts shell out to a bare `node` (e.g. electron-winstaller's select-7z-arch.js). When launched from the desktop updater chain (Desktop -> hermes-setup -> hermes update) the shell PATH customizations are lost, so the install dies with `'node' is not recognized` / `node: not found`. - cmd_gui: wrap the npm-install env with with_hermes_node_path(_nixos_build_env()) so managed Node is prepended even on a stripped PATH — mirrors the idiom already used by the update deps refresh. (The original fix merged nixos_env on TOP of the managed env, whose full os.environ copy clobbered the managed PATH back to bare; wrapping fixes that merge order.) - _cmd_update_impl: spawn the `desktop --build-only` subprocess with with_hermes_node_path() so the child starts with managed Node from the outset. Regression test: the desktop install env now prepends the managed Node dir ahead of a bare updater PATH instead of passing env=None. Co-authored-by: F4TB0Yz <jfduarte09@gmail.com>