Can I vibecode Gmelius?

Build a detailed, self-hosted clone inspired by Gmelius focusing on its core email collaboration capabilities. Use exactly this stack: Tauri 2, React, TypeScript, Tailwind CSS, SQLite, and Prisma ORM.

**DATA MODEL & SCHEMA SPECIFICS**
Implement the following core entities in SQLite:
- `accounts`: `id`, `email`, `imap_host`, `smtp_host`, `encrypted_credentials`.
- `threads`: `id`, `account_id`, `subject`, `status` (enum: open, pending, closed), `assignee_id`.
- `messages`: `id`, `thread_id`, `sender`, `recipient`, `body`, `received_at`.
- `internal_notes`: `id`, `thread_id`, `author_id`, `content`, `created_at`.
Ensure all relations have cascading deletes where appropriate. Use foreign key constraints.

**SCREENS & UX PATTERNS**
1. **Kanban Board (`/board`)**: Visual columns (Open, Pending, Closed) representing thread states. Drag-and-drop threads between columns.
2. **Shared Inbox (`/inbox`)**: A split-pane layout with a left sidebar for folders/labels, middle column for thread lists, and a right pane for reading messages.
3. **Thread View (`/thread/[id]`)**: Displays a chronological list of emails interwoven with distinct UI blocks for internal team notes. Include a rich-text reply composer at the bottom.
4. **Settings Panel (`/settings`)**: A modal for configuring IMAP/SMTP credentials and managing local team members.

**STEP-BY-STEP USER JOURNEYS**
- **Journey 1 (Onboarding)**: User launches the app, enters IMAP/SMTP details, and the app begins syncing emails locally in the background.
- **Journey 2 (Collaboration)**: User selects an email thread, clicks "Add Note", types a markdown-formatted internal comment, and tags a local team member.
- **Journey 3 (Organization)**: User drags an email thread from the 'Open' column to the 'Closed' column in the Kanban view, automatically updating the thread's local state.
- **Journey 4 (Action)**: User replies to a customer from within the shared thread; the app sends it via the configured SMTP server and appends it to the thread.

**TECHNICAL SPECIFICATIONS & PROTOCOLS**
- Use local IMAP syncing via standard Node.js/Rust libraries to fetch and parse raw MIME messages.
- Use SMTP for sending outgoing replies.
- Implement optimistic UI updates for instant feedback during list operations (like assigning an email).
- Data export functionality: Provide a utility to generate standard EML files for downloaded messages.
- Ensure sensitive IMAP credentials are encrypted at rest using system-level secure storage accessible via Tauri APIs.

Start from an empty folder, create the complete project, and ensure the default mode is single-user and private. Do not add analytics or telemetry. Put all secrets in `.env`. Validate untrusted input. Write unit tests for the core logic and one end-to-end smoke test. Run the tests and build before finishing.