Android: app shell + Custom Settings engine + Home Assistant integration

Generic settings architecture (data-driven, no per-setting UI code):
- SettingDefinition (id/name/description/category/type/default/min/max/
  choices/editable/sensitive/requiresRestart/visibleIf) x 8 types:
  boolean/string/number/select/multi-select/color/url/secret
- SettingsManager: validation, reset, custom CRUD, export/import
  (all-or-nothing with per-key rejection reasons; custom definitions
  travel in the export), secrets routed to EncryptedSharedPreferences
  (AndroidKeyStore master key) and excluded from export by default
- Settings screen renders controls from the type; search; add/edit/delete
  dialogs for custom settings; import/export dialogs
- Built-ins: General / Home Assistant / Appearance / Network / Advanced

Home Assistant integration (official REST + WebSocket APIs only):
- HomeAssistantClient: GET /api/, /api/states, /api/states/{id},
  POST /api/services/{domain}/{service}, WS /api/websocket
  (auth -> subscribe_events state_changed) with exponential-backoff
  reconnect; safe HaError types that never contain the token
- HaRepository: single service layer between UI and client; optimistic
  toggles reconciled by WS; poll fallback from refresh-interval setting
- Devices screen: discovery list, search, live states, toggles
  (light/switch/fan/input_boolean/humidifier)
- Cleartext permitted for LAN http:// URLs (same stance as the official
  HA companion app; TLS verification untouched); consent dialog on first
  launch; Record button present but inert until M4 (honest label)
- Tests: 29 unit tests (19 settings incl. secret routing, import
  validation, persistence; 10 HA via MockWebServer incl. 401 handling,
  unreachable, WS handshake + event + auth_invalid). All green.

Docs: docs/home-assistant.md (install, token creation, storage,
troubleshooting, endpoint table); README + ROADMAP updated honestly
(live e2e against a real HA server still in progress).

README.md

@@ -57,10 +57,18 @@ adb install app/build/outputs/apk/debug/app-debug.apk
 S.H.O.N.A.R. is developed in milestones; each merged milestone is tested and
 buildable. See [docs/ROADMAP.md](docs/ROADMAP.md) for the maintained matrix.
 
-**Current state:** M0–M1 complete — backend health, full auth (register,
-login, rotating refresh tokens with reuse detection, logout, delete-account),
-rate limiting, Alembic schema, Docker dev stack. Everything else is
-in-progress or TODO as per the roadmap.
+**Current state:**
+
+- Backend: M0–M2 complete — health, full auth (register, login, rotating
+  refresh tokens with reuse detection, logout, delete-account), rate
+  limiting, chunked resumable uploads, recordings CRUD, storage
+  abstraction, Postgres FTS schema, Docker dev stack.
+- Android: app shell with a generic data-driven **Custom Settings** system
+  (8 value types, add/edit/delete/reset/search/export/import), and a full
+  **Home Assistant** integration — connect, test, entity discovery, live
+  WebSocket state updates, service calls (toggles), encrypted token
+  storage. See [docs/home-assistant.md](docs/home-assistant.md).
+- Recording engine, SHONAR sync, playback, AI pipeline: TODO per roadmap.
 
 ## AI providers