docs: make Android native app the primary target

docs/ARCHITECTURE.md

@@ -5,7 +5,8 @@
 Hermes Mobile is split into two deployable parts:
 
 1. Mobile app
-   - Installable PWA designed for Android.
+   - Native Android app built with Capacitor around a shared React UI.
+   - PWA/web build remains available as fallback and dev target.
    - Talks only to the companion server.
    - Does not need direct access to Hermes files or credentials.
 
@@ -16,7 +17,7 @@ Hermes Mobile is split into two deployable parts:
 
 ```text
 +---------------------------+
-| Android PWA               |
+| Android App               |
 | - Chat                    |
 | - Tool timeline           |
 | - Cron UI                 |
@@ -24,7 +25,7 @@ Hermes Mobile is split into two deployable parts:
 | - Approvals               |
 +-------------+-------------+
               |
-              | HTTPS REST + WebSocket/SSE + Web Push
+              | HTTPS REST + WebSocket/SSE + native push/Web Push fallback
               v
 +---------------------------+
 | Hermes Companion Server   |
@@ -303,9 +304,11 @@ Providers:
 - systemd service.
 - Better production posture.
 
-## Future Native Wrapper
+## Native Android Shell
 
-If Android PWA is insufficient:
-- Add Capacitor app under `apps/android-shell`.
-- Reuse same web app.
-- Gain native share target, richer push, microphone/file APIs.
+Capacitor Android is part of the primary architecture, not a future contingency.
+
+- The shared React UI builds into `apps/mobile/dist`.
+- Capacitor packages that build into an Android APK.
+- PWA/web access remains useful for dev, desktop, and fallback.
+- Native plugins provide share target, richer push, haptics, status bar, splash screen, microphone/file improvements, and Android lifecycle hooks.