docs: update README + docs site for public readiness

Refresh the README and documentation for public visitors:

- README: public-facing rewrite with accurate status for all four native
  clients (macOS, Linux, Windows, Android) and the Windows host.
- docs site: fix stale client status (Android is a full client, not a
  scaffold; Windows client is stage-1 complete + signed MSIX), add the
  missing Android client section, correct "which client" guidance.
- Windows host: corrected from "deferred/scoped" to implemented & shipping
  (NVIDIA-only, x64-only) across windows-host, roadmap, status,
  requirements, running-as-a-service, and the README.
- Remove internal infrastructure from public docs (box names, private IPs,
  SSH/token commands, deploy topology); rewrite status.md as a public
  project-status page; sanitize ci.md and implementation-plan.md.
- Update clients/android and clients/apple READMEs to current state.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

docs-site/content/docs/troubleshooting.md

@@ -65,8 +65,9 @@ Then log out and back in. On other distros this is `sudo usermod -aG input $USER
 
 ## Stutter, drops, or high latency
 
-- Lower the **bitrate**. On a busy or Wi-Fi link, the requested bitrate may be too high — the Apple
-  app's [speed test](/docs/configuration#bitrate) picks a safe value; with Moonlight, set it manually.
+- Lower the **bitrate**. On a busy or Wi-Fi link, the requested bitrate may be too high — the native
+  clients' [speed test](/docs/configuration#bitrate) picks a safe value; with Moonlight, set it
+  manually.
 - Prefer a **wired** connection or 5 GHz Wi-Fi between host and client.
 - Streaming to **many devices at once** shares the GPU encoder. The production host
   (`serve --native`) handles one native session at a time, with extra clients queued; heavy load is