Can I vibecode Twist?

Build a personal replacement for Twist in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, WebSockets, and Docker Compose; do not offer alternative stacks.
The core loop is: host a private space for asynchronous team threads, organize discussion into structured channels and topics, and keep membership and moderation under the owner's control. The fundamental value proposition is 'productivity over presence'—a calm, distraction-free environment for deep work.
The visual design must be exceptionally premium and tranquil. Use a curated, harmonious color palette featuring soft, modern tones and a beautiful dark mode. Typography must be highly legible and elegant (e.g., Inter or Outfit) to support long-form reading. Avoid any generic styling; utilize subtle glassmorphism, refined borders, and gentle micro-animations for interactions like expanding threads or adding reactions. The UI must feel completely distinct from high-anxiety, real-time chat apps.
Crucially, enforce an asynchronous focus: completely omit presence indicators (no 'green dots' for online status) and typing indicators. Implement a highly structured, thread-based conversation model where every discussion requires a subject line to prevent information from getting lost in a stream of chat.
Include robust, searchable historical records of all threads. Add a dedicated 'Inbox' or customizable notification view that encourages batch-processing of updates rather than instant interruptions.
Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials.
Implement spaces, channels, topics, replies, reactions, mentions, profiles, roles, and invitations. Use WebSockets for live updates but preserve every message transactionally in PostgreSQL.
Add moderation queues, reports, blocks, rate limits, attachment limits, and an audit log. Provide email digests, browser notifications, search, pinned content, and member export. Add owner-controlled retention, account deletion, backup, restore, and health checks.
Ship Docker Compose with a seeded demo, migrations, and an emergency admin command. Include clear, beautifully designed empty, loading, success, and recoverable error states.
Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out public-network discovery, production voice or video rooms, and real-time chat features.
Finish by running the tests and listing the exact commands used.