Can I vibecode Hiver?

Build a detailed, self-hosted clone inspired by Hiver focusing on its core Gmail-like shared inbox 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`, `oauth_token`, `refresh_token`.
- `shared_labels`: `id`, `name`, `color_code`.
- `threads`: `id`, `account_id`, `gmail_thread_id`, `subject`, `assignee_id`, `status` (open, pending, closed).
- `messages`: `id`, `thread_id`, `gmail_message_id`, `body`, `timestamp`.
- `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. **Gmail-like Interface (`/inbox`)**: A layout mirroring classic webmail. Left sidebar for shared labels (e.g., Support, Sales); main area showing a dense list of threads with assignee avatars.
2. **Thread Detail (`/thread/[id]`)**: Displays messages in an accordion format. A distinct, color-coded sticky bar at the top allows changing assignment and status.
3. **Notes Panel**: A right-hand side drawer specifically for internal team chat/notes related to the current thread.
4. **Settings Panel (`/settings`)**: A modal for managing shared labels, routing rules, and local user aliases.

**STEP-BY-STEP USER JOURNEYS**
- **Journey 1 (Onboarding)**: User authenticates via IMAP/SMTP, and the app begins syncing emails locally in the background, matching them to shared labels.
- **Journey 2 (Triage)**: User views the "Unassigned" list, selects a thread, and uses a dropdown in the sticky header to assign it to themselves, moving it to "Mine".
- **Journey 3 (Collaboration)**: User opens a thread, types a markdown-formatted internal comment in the side drawer, and tags a local team member for help.
- **Journey 4 (Action)**: User drafts a reply from within the shared thread; the app sends it via the configured SMTP server, appends it to the thread, and optionally marks it as closed.

**TECHNICAL SPECIFICATIONS & PROTOCOLS**
- Use local IMAP syncing via standard 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 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.