refactor(openclaw): delegate gateway to OS service manager with Windows compatibility

[DeJeune]

What this PR does

Refactors OpenClawService to delegate gateway lifecycle to the OS service manager (launchd/systemd) via OpenClaw CLI commands, with platform-specific handling for Windows.

Core changes:

• Gateway lifecycle delegated to OS service manager via openclaw gateway install/start/stop/restart/status/health CLI commands
• Removes in-process ChildProcess management, node:net Socket probing, and killProcess helper
• Health checks use openclaw gateway health CLI command
• getStatus is now async and probes health to detect externally-started gateways
• Return type unified to discriminated union OperationResult = { success: true } | { success: false; message: string }

Windows-specific handling:

• Skip gateway install/uninstall (scheduled task integration has upstream bugs)
• Gateway started via openclaw gateway start --force (same as macOS/Linux, but without service registration)
• Port conflict detection before startup with clear error messages
• NPM_CONFIG_SCRIPT_SHELL=cmd.exe for npm install compatibility

Install improvements:

• Auto-install Node.js 22+ if missing (brew/pacman/apt/dnf/winget/choco/scoop)
• Auto-install Git if missing (best-effort, non-blocking)
• Force HTTPS for git during npm install (GIT_CONFIG env vars) to avoid SSH key failures
• China npm mirror acceleration for users in China
• EACCES retry with sudo-prompt on macOS/Linux
• Streaming output to UI throughout all steps
• GBK decoding for Chinese Windows cmd.exe output

UI improvements:

• Copy button on install/uninstall log container
• Copy button on error alert messages
• Selectable error text
• Fix Start button stuck in loading state on failure

Why we need it and why it was done in this way

• Delegating to OS service management (launchd/systemd) is more robust — the gateway survives app restarts and can be managed externally
• Using CLI commands for health checks aligns with OpenClaw's own tooling and avoids false positives
• Windows skips service registration because the scheduled task integration has too many upstream bugs, but still uses CLI commands for start/stop/status/health
• Direct npm install (instead of official install scripts) gives full control and avoids platform-specific script issues (cmd.exe quote stripping, TLS, PowerShell execution)

Breaking changes

None. Internal refactoring only — no user-facing API changes.

Special notes for your reviewer

• Windows: no service registration (gateway install/uninstall skipped via !isWin guards), gateway started with gateway start --force, port checked before startup
• macOS/Linux: full service lifecycle (gateway install after npm install, ensureGatewayServiceInstalled on startup, uninstallGatewayService before npm uninstall)
• Auth token synced to both openclaw.cherry.json and default openclaw.json so system services can read it
• OperationResult is a proper discriminated union in @shared/config/types

Checklist

• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Documentation: A user-guide update was considered and is present (link) or not required.
• Self-review: I have reviewed my own code before requesting review from others

Release note

NONE

[DeJeune]

Review Summary

The OperationResult discriminated union and dead field cleanup are clean improvements. The type change is well-applied across main, preload, and renderer store. Good work.

Issues Found

Bug (1):

• checkHealth() has an early-return guard (gatewayStatus !== 'running') that makes getStatus() external gateway detection and startAndWaitForGateway() health polling dead code. Needs a private probe method without the guard.

Significant (1):

• restartGateway ignores the command result and always returns success.

Minor (2):

• OperationResult is redeclared in preload as OpenClawOperationResult — consider a shared type.
• gatewayUrl visibility/path changes are unrelated to the refactor scope.

Positives

• Discriminated union is the right pattern here — TypeScript narrows cleanly
• All renderer callers already used the correct !result.success check pattern, so no caller changes needed
• Dead uptime/version fields properly removed across all three layers

[DeJeune]

Significant: restartGateway fires gateway restart but ignores the result — if the command fails (non-zero exit or timeout), it still returns { success: true }. Should check the result:

const { code, stderr } = await this.execOpenClawCommandWithResult(openclawPath, ['gateway', 'restart'], shellEnv)
if (code \!== 0) {
  this.gatewayStatus = 'error'
  return { success: false, message: stderr.trim() || `Restart failed with code ${code}` }
}