docs: clarify android support status

CHANGELOG.md

@@ -11,7 +11,8 @@ project follows [Semantic Versioning](https://semver.org/).
 - **Analytics validation runbook.** Documented native Matomo live validation,
   expected event payloads, and the current web/WASM analytics split.
 - **Android smoke-test runbook.** Updated the Android doc with the current
-  platform status and a physical-device launch/touch/safe-area checklist.
+  platform status, support matrix, and a physical-device
+  launch/touch/safe-area checklist.
 - **Browser Bevy canvas route and automation support.** Added the `solitaire_web`
   Bevy WASM build, wired `/play` to the Bevy canvas, added a
   `window.__FERROUS_DEBUG__` bridge, and introduced Playwright coverage for the

docs/ANDROID.md

@@ -2,8 +2,8 @@
 
 This doc captures the toolchain install + build invocation for the
 Android target. Steps are runnable on a fresh Debian 13 (trixie) box;
-later sections document what's known to compile, what's stubbed, and
+later sections document physical-device validation, supported platform
-the next milestones.
+surfaces, and remaining Android follow-ups.
 
 > **Status (2026-06-09):** Android build plumbing, app-directory storage,
 > JNI keystore wiring, and safe-area layout fixes have landed. The remaining
@@ -220,7 +220,7 @@ and note the exact screen/control path that reproduced it.
 
 ---
 
-## 5. What's wired vs. what's stubbed
+## 5. Platform support matrix
 
 Desktop-only crates and call sites are gated so the workspace cross-compiles.
 Each gate is documented at its call site.
@@ -233,7 +233,7 @@ Each gate is documented at its call site.
 | Data directory | Platform data dir | Android app files dir |
 | App entry point | `bin` target → `solitaire_app::run()` | `cdylib` target loaded by NativeActivity |
 
-What's not yet ported / not yet measured:
+Remaining Android follow-ups:
 
 - Touch UX pass — hit-target sizes, modal scaling on small screens,
   app lifecycle (suspend / resume), font scaling.