fix(windows): broken PATH propagation, ps usage, and claude binary resolution

- sherpa-runtime-env: use case-insensitive key lookup when modifying PATH
  on plain env objects. On Windows, `{...process.env}` stores PATH as
  `Path` but `applySherpaLoaderEnv` used hardcoded `"PATH"`, creating a
  duplicate key that could shadow the real system PATH in child processes.

- runtime-toolchain: use `wmic` on Windows instead of Unix-only `ps -o`
  to resolve the node executable path from a PID.

- claude-agent: pass `findExecutable("claude")` as
  `pathToClaudeCodeExecutable` so the SDK uses the user's installed
  binary when available. Update spawn hook to only replace bare
  "node"/"bun" with process.execPath, preserving native binary paths.

- desktop/paseo.cmd: use ELECTRON_RUN_AS_NODE with node-entrypoint-runner
  for the Windows CLI wrapper.

packages/server/src/server/agent/providers/claude-agent.ts

@@ -67,7 +67,11 @@ import type {
   McpServerConfig,
   PersistedAgentDescriptor,
 } from "../agent-sdk-types.js";
-import { applyProviderEnv, type ProviderRuntimeSettings } from "../provider-launch-config.js";
+import {
+  applyProviderEnv,
+  findExecutable,
+  type ProviderRuntimeSettings,
+} from "../provider-launch-config.js";
 import { getOrchestratorModeInstructions } from "../orchestrator-instructions.js";
 
 const fsPromises = promises;
@@ -201,11 +205,14 @@ function applyRuntimeSettingsToClaudeOptions(
     ...options,
     spawnClaudeCodeProcess: (spawnOptions) => {
       const resolved = resolveClaudeSpawnCommand(spawnOptions, runtimeSettings);
-      // The SDK defaults to spawning "node" via PATH lookup, which fails when
-      // running from the managed runtime bundle where node isn't in PATH.
-      // Always use process.execPath — the actual node binary running the daemon.
-      const command =
-        resolved.command === spawnOptions.command ? process.execPath : resolved.command;
+      // When the SDK passes a default JS runtime ("node"/"bun"), replace it with
+      // process.execPath — the actual node binary running the daemon. This avoids
+      // PATH lookup failures in the managed runtime bundle.
+      // When the SDK passes a native binary path (from pathToClaudeCodeExecutable)
+      // or the user overrides the command via runtime settings, use that directly.
+      const isDefaultRuntime =
+        resolved.command === "node" || resolved.command === "bun";
+      const command = isDefaultRuntime ? process.execPath : resolved.command;
       const child = spawn(command, resolved.args, {
         cwd: spawnOptions.cwd,
         env: {
@@ -1855,12 +1862,14 @@ class ClaudeAgentSession implements AgentSession {
       .filter((entry): entry is string => typeof entry === "string" && entry.length > 0)
       .join("\n\n");
 
+    const claudeBinary = findExecutable("claude");
     const base: ClaudeOptions = {
       cwd: this.config.cwd,
       includePartialMessages: true,
       permissionMode: this.currentMode,
       agents: this.defaults?.agents,
       canUseTool: this.handlePermissionRequest,
+      ...(claudeBinary ? { pathToClaudeCodeExecutable: claudeBinary } : {}),
       // Use Claude Code preset system prompt and load CLAUDE.md files
       // Append provider-agnostic system prompt and orchestrator instructions for agents.
       systemPrompt: {

packages/server/src/server/speech/providers/local/sherpa/sherpa-runtime-env.ts

@@ -70,6 +70,21 @@ export function resolveSherpaLoaderEnv(
   }
 }
 
+/**
+ * Find the actual case-sensitive key in a plain object that matches the given
+ * key case-insensitively. On Windows, `{...process.env}` produces a plain
+ * (case-sensitive) object where PATH is typically stored as `Path`. Using a
+ * hardcoded `"PATH"` would miss the existing key and create a duplicate,
+ * breaking the child process's PATH.
+ */
+function findEnvKey(env: NodeJS.ProcessEnv, key: string): string {
+  const lower = key.toLowerCase();
+  for (const k of Object.keys(env)) {
+    if (k.toLowerCase() === lower) return k;
+  }
+  return key;
+}
+
 export function applySherpaLoaderEnv(
   env: NodeJS.ProcessEnv,
   platform: NodeJS.Platform = process.platform,
@@ -90,9 +105,10 @@ export function applySherpaLoaderEnv(
     };
   }
 
-  const next = prependEnvPath(env[resolved.key], resolved.libDir);
-  const changed = next !== (env[resolved.key] ?? "");
-  env[resolved.key] = next;
+  const actualKey = findEnvKey(env, resolved.key);
+  const next = prependEnvPath(env[actualKey], resolved.libDir);
+  const changed = next !== (env[actualKey] ?? "");
+  env[actualKey] = next;
   return {
     changed,
     key: resolved.key,