Can I vibecode Woodpecker?

Build a closest honest personal substitute for Woodpecker in an empty repository.
Use Next.js 15 (App Router), TypeScript, Tailwind CSS, PostgreSQL (via Drizzle ORM), BullMQ, and Nodemailer (for SMTP sending); do not offer alternative stacks.

DATA MODEL:
- `Prospect`: id, email, first_name, company, custom_fields (json), status (active, replied, bounced, opted_out)
- `Campaign`: id, name, email_account_id, status (draft, running, paused)
- `EmailStep`: id, campaign_id, step_number, subject_template, body_template, delay_days, condition (e.g., 'if_not_opened', 'if_not_replied')
- `SendLog`: id, prospect_id, email_step_id, sent_at, opened_at, clicked_at

USER JOURNEYS & SCREENS:
1. **Email Accounts & Deliverability (`/accounts`)**: A setup screen to connect SMTP/IMAP credentials. Include a "Test Connection" button and a visual indicator of daily sending limits and domain reputation health.
2. **Campaign Creator (`/campaigns/new`)**: A step-by-step wizard. Step 1: Add Prospects (upload CSV mapping columns to `Prospect` fields). Step 2: Write Emails (a rich text editor supporting variable injection like {{first_name}}). Step 3: Set Schedule (define sending windows, e.g., Mon-Fri 9AM-5PM EST).
3. **Campaign Overview (`/campaigns/{id}`)**: A detailed view showing stats (Sent, Opened, Clicked, Replied, Bounced). Contains tabs to view the specific prospects in each stage.
4. **Central Inbox (`/inbox`)**: A unified view fetching replies via IMAP. Automatically detects replies to pause the corresponding sequence and marks the `Prospect` status as 'replied'.

TECHNICAL SPECIFICATIONS:
- Sending Engine: Use BullMQ for the sending queue. Implement an algorithm that disperses sending evenly over the defined business hours (adaptive sending) to avoid spam filters, rather than sending in batches.
- Variable Interpolation: Implement a robust template parser that replaces {{variables}} and falls back to default values if the prospect's field is missing.
- Bounce & Reply Detection: Run a background worker that polls the connected IMAP inbox for bounces (parsing standard DSN messages) and real replies, updating `Prospect` status and stopping the sequence.
- Deliverability Safeguards: Prevent sending if the email format is invalid. Ensure all outgoing emails include an unsubscribe link that automatically sets `status` to 'opted_out'.

Store all user data locally by default.
Put secrets in .env, ship .env.example.
Provide contact fields, tags, and a complete change history.
Write focused tests for the IMAP polling logic, template interpolation, and adaptive sending algorithm.
Create a README with setup, architecture, and backup steps.
Do not add automated inbox warm-up networks.