openclaw - 💡(How to fix) Fix Windows native: shell env fallback failed with spawnSync /bin/sh ENOENT [2 pull requests]

Describe the bug When running OpenClaw 2026.5.19 on native Windows (not WSL2), the following warning appears during startup:

[openclaw] shell env fallback failed: spawnSync /bin/sh ENOENT

To Reproduce Steps to reproduce the behavior:

1. Install OpenClaw 2026.5.19 on native Windows
2. Run openclaw or openclaw status
3. See the warning about /bin/sh ENOENT

Expected behavior OpenClaw should detect Windows platform and skip the shell env fallback that relies on /bin/sh, which doesn't exist on Windows.

Environment:

• OS: Windows 10/11 (native, not WSL2)
• OpenClaw version: 2026.5.19

Root Cause In src/infra/shell-env.ts, the probeLoginShellEnv function attempts to execute /bin/sh to probe the login shell environment. On Windows, this shell doesn't exist, causing the ENOENT error.

While getShellPathFromLoginShell already has a Windows platform check, probeLoginShellEnv (called by loadShellEnvFallback) does not have this check.

Proposed Fix Add a Windows platform check at the beginning of probeLoginShellEnv function:

function probeLoginShellEnv(params: {
  env: NodeJS.ProcessEnv;
  timeoutMs?: number;
  exec?: typeof execFileSync;
  platform?: NodeJS.Platform;
}): LoginShellEnvProbeResult {
  const platform = params.platform ?? process.platform;
  if (platform === "win32") {
    return { ok: true, shellEnv: new Map() };
  }
  // ... rest of the function
}

Additional context Related to the Windows native support improvements mentioned in the 5.19 release notes.