¿Puedo vibecodear Campaign Monitor?

Build a personal replacement for Campaign Monitor in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Amazon SES; do not offer alternative stacks.
The core loop is: collect and manage subscribers, compose and send branded compliant campaigns, publish a web archive, and report basic delivery and click events.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Implement subscriber import, double opt-in, unsubscribe, suppression, tags, and consent timestamps.
Create a Markdown campaign editor with HTML and plain-text previews.
Queue sends through SES with retries, rate limits, idempotency, and resumable batches.
Process delivery, bounce, complaint, open, and click webhooks without logging message content.
Publish a simple issue archive and subscriber preference page.
Add test sends, seed-list checks, DNS setup guidance, exports, and backups.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a newsletter recommendation marketplace.
Deliberately leave out ad sales and payment infrastructure.
Deliberately leave out complex lifecycle automation and enterprise deliverability support.
Finish by running the tests and listing the exact commands used.