feat(web): complete groups/contacts/favorites/settings/calls/system domains + extensive review-round fixes

Rounds out the full rewrite with the remaining feature domains: group
management (admin panel, mute, files, announcements, QR-based invite/join),
contacts (friend profile, add-friend, blocklist, new-friends), favorites
(real media rendering across text/image/video/voice/file/link), settings
(profile/security/privacy/general/about), calls (Agora-backed audio/video
signaling + call history), and system messages/file assistant.

Also folds in a large batch of live-verified fixes surfaced by repeated
fresh code-review passes and hands-on E2E testing against the real
backend, including: WS reconnect not resubscribing any topic after a
disconnect, missing x-im-client-mid on every send path (protocol
compliance for retry dedup), group mute/member-settings/self-profile
endpoint corrections, relationship-state type fixes across search/QR/
friend-profile, tenant-switch logout gap, password-policy now read from
the real per-tenant config instead of guessed, NavRail highlight/
aria-current desync, several call-state-machine races, and responsive
layout fixes across all four breakpoints (mobile/tablet/laptop/desktop)
including a full mobile rebuild of favorites, call UI, and the settings
home/sub-list split.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

web/src/lib/api/messages.ts

@@ -1,6 +1,8 @@
 // Message-level REST endpoints that sit alongside the native WS protocol. Recall goes through REST
 // (not a Tinode WS operation) -- ported from the old app's context-menu.jsx recallOwnMessage, which
 // calls this then hard-deletes the message from the local topic cache itself.
+import type { DraftyContent } from 'tinode-sdk';
+
 import { imGet, imPost } from './client';
 
 export interface RecallResult {
@@ -57,7 +59,12 @@ export interface SearchHit {
   matches?: Array<{ start: number; end: number }>;
   snippet?: string;
   snapshot?: {
-    content?: { txt?: string; fmt?: unknown[]; ent?: DraftyEntity[] };
+    // A plain, unformatted text message's `content` is confirmed LIVE to arrive as a bare string
+    // (not the `{txt,fmt,ent}` object shape this field was originally typed as) -- the same
+    // string-vs-object duality `renderDrafty` (lib/messages/drafty.tsx) already handles for every
+    // other Drafty consumer in this app, discovered here because a real search hit for a plain-text
+    // message rendered as blank space until this was fixed (see HistorySearchModal's SnapshotContent).
+    content?: DraftyContent | string;
   };
 }