Can I vibecode Helpwise?

Build a detailed, self-hosted clone inspired by Helpwise focusing on its core 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:
- `inboxes`: `id`, `name`, `email_address`, `imap_settings`, `smtp_settings`.
- `conversations`: `id`, `inbox_id`, `customer_email`, `subject`, `status` (open, closed, spam), `assignee_id`.
- `emails`: `id`, `conversation_id`, `message_id`, `direction` (inbound, outbound), `html_body`, `timestamp`.
- `comments`: `id`, `conversation_id`, `author_id`, `text`, `created_at`.
Ensure all relations have cascading deletes where appropriate. Use foreign key constraints.

**SCREENS & UX PATTERNS**
1. **Inbox View (`/inbox/[id]`)**: A classic three-pane layout. Left pane lists all inboxes/tags; middle pane shows a scrollable list of conversations; right pane displays the active conversation.
2. **Conversation Thread (`/conversation/[id]`)**: Shows a timeline of emails and internal comments. Features a collision detection banner ("User X is viewing this").
3. **Reply Composer**: A persistent editor at the bottom of the conversation view with support for rich text, attachments, and canned responses.
4. **Settings Panel (`/settings`)**: A slide-over drawer containing tabs for Inbox Configuration, Canned Responses, and User Management.

**STEP-BY-STEP USER JOURNEYS**
- **Journey 1 (Onboarding)**: User adds a new shared inbox by providing IMAP/SMTP credentials. The app shows a progress bar while initially fetching the last 100 emails.
- **Journey 2 (Triage)**: User reviews the inbox list, selects multiple conversations using checkboxes, and applies a "bulk close" action to archive them.
- **Journey 3 (Collaboration)**: User opens a complex customer request, tags a team member in an internal comment, and assigns the conversation to them.
- **Journey 4 (Response)**: The assigned user writes a reply using a pre-saved canned response, sends the email, and the conversation automatically moves to 'closed' status.

**TECHNICAL SPECIFICATIONS & PROTOCOLS**
- Use local IMAP syncing via standard Rust/Node libraries to fetch and parse raw MIME messages.
- Use SMTP for sending outgoing replies.
- Implement collision detection using local polling or a lightweight WebSocket server if running in a networked environment.
- Data export functionality: Provide a utility to generate standard EML files for downloaded messages or CSVs for conversation metadata.
- 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.