Can I vibecode Boomerang for Gmail?

Build a deliberately narrow personal substitute for Boomerang for Gmail, not a full clone.
Use exactly this stack: Tauri 2 + React + TypeScript + SQLite.
Primary job: Build a local desktop email companion focused on inbox control, scheduling, and response tracking that works on one user-authorized IMAP/SMTP account.
Start from an empty folder and create the complete working project. Make the default mode single-user and private.

Data Model:
- `Accounts`: id, email, imap_host, smtp_host
- `Messages`: id, account_id, message_id, thread_id, subject, sender, snippet, date, is_read
- `ScheduledSends`: id, account_id, message_body, to_address, send_at, status (pending, sent, failed)
- `FollowUps`: id, message_id, trigger_condition (no_reply_by), trigger_date, status
- `InboxPauseStatus`: account_id, is_paused, unpause_at, allowed_senders (JSON)

User Journey & Screens:
1. Inbox View: A focused inbox interface with integrated tools on each thread.
2. Compose Screen: Includes a "Send Later" datetime picker and a "Remind me if no reply" toggle with a date selector.
3. Inbox Pause Dashboard: A toggle to temporarily hide incoming emails, with settings to allow exceptions (VIP senders) and schedule an automatic unpause time.
4. Scheduled/Tracked Dashboard: View all pending scheduled emails and follow-up reminders.

Technical specifics:
- Store credentials only in the OS keychain using Tauri plugins; store emails locally in SQLite.
- Implement an IMAP sync engine that can move incoming emails to a hidden folder when "Inbox Pause" is active, and move them back when unpaused.
- Implement a background scheduler loop to dispatch `ScheduledSends` via SMTP.
- Deliberately exclude these paid-product advantages: team routing and shared inbox rules; AI writing coach (Respondable); meeting scheduling features; calendar-provider edge cases.
- Write focused unit tests for the scheduling logic and follow-up triggers.
- Create a README with setup, permissions, architecture, data location, and limitations.
- Run the tests and build before finishing, then fix errors rather than merely describing them.