Can I vibecode EmailOctopus?

Build a personal replacement for EmailOctopus in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Amazon SES; do not offer alternative stacks.
The core loop is: manage a subscriber list with custom fields, compose simple newsletters using a drag-and-drop or block editor, and view basic real-time statistics.
Make the first run work locally with one documented command. Store all user data locally by default.

Data Model:
- `Lists`: id, name, description
- `Subscribers`: id, list_id, email, status (subscribed, unsubscribed, bounced)
- `CustomFields`: id, list_id, field_name, field_type
- `SubscriberData`: subscriber_id, field_id, value
- `Campaigns`: id, list_id, subject, content_html, status, sent_at
- `CampaignStats`: campaign_id, total_sent, opens, clicks, bounces

User Journey & Screens:
1. List & Subscriber Management: View a specific list, import via CSV, and add custom fields. Screen to view an individual subscriber's data.
2. Campaign Editor: A clean, intuitive email creator (WYSIWYG) that supports basic personalization using merge tags (e.g., {{FirstName}}).
3. Reporting Screen: Basic real-time statistics showing open rates, click rates, and bounce counts per campaign.

Technical specifics:
- Queue sends through SES with retries, rate limits, idempotency, and resumable batches.
- Process delivery, bounce, complaint, open, and click webhooks from SES.
- Implement double opt-in and automated unsubscribe handling.
- Deliberately leave out: complex behavioral triggers, deep e-commerce sync, predictive analytics, complex landing page builders. Focus on simple list management and broadcasting.
- Write focused tests for the merge-tag replacement logic and the CSV import process.
- Create a README with setup, architecture, permissions, and SES webhook configuration steps.
- Run the tests and build before finishing, then fix errors rather than merely describing them.