docs: clarify native Windows support alongside WSL2 across getting-started, windows, and onboarding-overview

docs/platforms/windows.md

@@ -1,22 +1,22 @@
 ---
-summary: "Windows (WSL2) support + companion app status"
+summary: "Windows support: native and WSL2 install paths, daemon, and current caveats"
 read_when:
   - Installing OpenClaw on Windows
+  - Choosing between native Windows and WSL2
   - Looking for Windows companion app status
-title: "Windows (WSL2)"
+title: "Windows"
 ---
 
-# Windows (WSL2)
+# Windows
 
-OpenClaw on Windows is recommended **via WSL2** (Ubuntu recommended). The
-CLI + Gateway run inside Linux, which keeps the runtime consistent and makes
-tooling far more compatible (Node/Bun/pnpm, Linux binaries, skills). Native
-Windows might be trickier. WSL2 gives you the full Linux experience — one command
-to install: `wsl --install`.
+OpenClaw supports both **native Windows** and **WSL2**. WSL2 is the more
+stable path and recommended for the full experience — the CLI, Gateway, and
+tooling run inside Linux with full compatibility. Native Windows works for
+core CLI and Gateway use, with some caveats noted below.
 
 Native Windows companion apps are planned.
 
-## Install (WSL2)
+## WSL2 (recommended)
 
 - [Getting Started](/start/getting-started) (use inside WSL)
 - [Install & updates](/install/updating)