Android parity: formatting, notifications inbox, resend verification, push sync

docs/backend-web-android-parity.md

@@ -18,28 +18,21 @@ Backend покрывает web-функционал почти полность
 ## 2) Web endpoints not yet fully used on Android
 
 - `GET /api/v1/messages/{message_id}/thread` (data layer wired, UI thread screen/jump usage pending)
-- `GET /api/v1/notifications`
-- `POST /api/v1/notifications/push-token`
-- `DELETE /api/v1/notifications/push-token`
-- `POST /api/v1/auth/resend-verification`
 
 ## 2.1) Web feature parity gaps not yet covered on Android
 
-- Text formatting in composer/render is not at web parity yet:
-  - bold / italic / underline / strikethrough
-  - spoiler / monospace / code block / links
-  - shortcut/toolbar UX similar to web composer
+- Notification delivery polish is still partial:
+  - chat-level grouping/snooze parity with web prefs (full)
+  - richer per-chat override UX alignment in Android settings
 
 ## 3) Practical status
 
 - Backend readiness vs Web: `high`
-- Android parity vs Web (feature-level): `~82-87%`
+- Android parity vs Web (feature-level): `~87-91%`
 
 ## 4) Highest-priority Android parity step
 
 Завершить следующий parity-блок:
 
 - `GET /api/v1/messages/{message_id}/thread` (UI usage)
-- notifications API + UI inbox flow
-- notifications delivery polish (channels/grouping/snooze/per-chat overrides parity with web prefs)
-- text formatting parity in chat composer/render
+- notification delivery polish (channels/grouping/snooze/per-chat overrides parity with web prefs)