Build a Discord Clone in Swift with AI

Build a polished, fully working native iOS app in SwiftUI named Concord: an original community chat app that recreates the core experience of Discord, but with its own name, its own original logo and its own color palette. Do NOT use the Discord name, logo, wordmark, app icon or any trademarked asset anywhere in the app. Design an original Concord logo mark, drawn with SwiftUI shapes (Path/Canvas) or made as a generated image asset, and use it in the header.

Screens and flows (dark slate theme with your own accent, e.g. teal #14B8A6, not blurple; bottom bar: Servers, Messages, Notifications, You):
1. Servers home (the mobile layout): a left server rail with round server icons (original art or emoji + gradients), a selected-server pill indicator on the left edge, unread dots and mention badges, a Messages button on top, and "+" add server / explore at the bottom. To the right, the selected server's panel: banner, server name with boost level, "Invite" and search, and channel categories that collapse/expand: TEXT CHANNELS (# welcome, # announcements, # general, # show-your-app, # help, # memes), VOICE CHANNELS (🔊 Lounge with 3 people inside shown under it, 🔊 Coworking). Unread channels are white and bold. 5 servers, each with its own channels and messages ("Indie Builders", "Pixel Art Club", "Lo-fi Lounge", "Gym Rats", "Design Crit").
2. Channel chat: tapping a channel slides the chat panel in over the server list (swipe right or tap back to reveal the list again). Header "# general" with topic, threads, members icons. Messages are grouped by author with avatar, name in a role color, timestamp, replies with a quoted line, @mentions highlighted, a code block, a link embed card with an image, an image attachment, and reaction chips (tap to toggle your reaction and count; long-press a message opens an action sheet with an emoji row, Reply, Copy Text, Pin, Mark Unread). Composer: "+" button, "Message #general" input, emoji and send; sending adds your message with an animation, then "Kai is typing..." and a reply after about 2 s. At least 40 fixture messages across channels.
3. Members: the members icon (or swipe left in the chat) shows the member list grouped by role ("Mods — 2", "Online — 12", "Offline — 30") with status dots and activities ("Playing Pixel Quest"); tapping a member opens a profile sheet with banner, avatar, about me, roles and "Message".
4. Voice channel: tapping 🔊 Lounge opens a voice room: participant tiles with avatars and an animated green ring for whoever is "speaking" (rotate the speaker every couple of seconds), names, mute icons, and controls (camera off, mute toggle, deafen toggle, speaker, red leave). Leaving returns to the server with you removed from the channel's list.
5. Messages: DM list with online status and last message; open a DM and chat like a channel. Notifications: mentions and replies list. You: banner and avatar with a status picker (Online, Idle, Do Not Disturb, Invisible), username, "Set a custom status", and settings rows.

Rules for the whole app:
- Native SwiftUI for iOS 26, the deployment target the Vibecode iOS template already uses (do not change it). iPhone-first layout. SF Symbols are fine for UI icons (never for the Discord logo or any brand mark).
- Everything runs on-device from realistic, deterministic fixture data in one Swift file (e.g. Fixtures.swift: real-sounding names, handles, numbers, timestamps, captions). No backend (leave the backend/ folder alone and make no network calls except loading images and media), no login, no permissions (no camera, photos, location, contacts, notifications, microphone). Do not persist state (no UserDefaults, @AppStorage, SwiftData or files): every launch starts from the same fixture state, so the demo is repeatable.
- Remote images: load images.unsplash.com photo URLs (with ?w=800&q=80 style params) with AsyncImage (or a small cached image view) and a tasteful placeholder. Verify every image and media URL with `curl -s -o /dev/null -w "%{http_code}" <url>` before you use it and replace any that do not return 200. No broken or blank images anywhere.
- Polish: native-feeling spacing and typography, safe areas, smooth spring animations (.spring/.snappy, most under 350 ms), matchedGeometryEffect for hero and expand/collapse transitions where it helps, .sensoryFeedback haptics on key taps, pressed states, and loading/empty states. Simulated waits stay short (under 3 s). Every button visible on screen does something sensible; nothing is a dead end.
- Keep the compiler happy: small files (under ~300 lines each), big view bodies split into subviews, and no long chained expressions, so nothing hits "unable to type-check this expression in reasonable time".
- It must build with zero errors and run in the iOS simulator with no crash. Walk through every flow above and fix anything broken.