Can I vibecode Waalaxy?

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

DATA MODEL:
- `Prospect`: id, first_name, last_name, linkedin_url, email, company, status (new, contacted, replied, bounced)
- `Campaign`: id, name, status (draft, active, paused, completed)
- `SequenceStep`: id, campaign_id, step_order, channel (linkedin, email), action (visit, connect, message, send_email), content, delay_days
- `ActionLog`: id, prospect_id, sequence_step_id, executed_at, result (success, error)

USER JOURNEYS & SCREENS:
1. **Prospect CRM (`/prospects`)**: A data table (use TanStack Table) showing imported leads. Include a "CSV Import" button and a multi-select feature to assign prospects to a `Campaign`.
2. **Campaign Builder (`/campaigns/new`)**: A visual drag-and-drop workflow builder (use React Flow). Users define a trigger (e.g., 'Added to Campaign') and chain steps like 'Send LinkedIn Connect', wait 2 days, 'Send Email'. 
3. **Inbox/CRM Sync (`/inbox`)**: A centralized view of replies (email replies fetched via IMAP, LinkedIn replies manually logged or fetched if API available). Clicking a reply shows the prospect's timeline.
4. **Analytics Dashboard (`/dashboard`)**: Charts displaying conversion rates (Acceptance Rate, Reply Rate) per campaign.

TECHNICAL SPECIFICATIONS:
- Scheduling Engine: Use Redis and BullMQ. A chron job evaluates active campaigns daily, checking the last `ActionLog` for each prospect and queuing the next `SequenceStep` if `delay_days` have passed.
- Multichannel Execution: 
  - For Email: Send using SMTP via Nodemailer. Implement tracking pixels to monitor open rates.
  - For LinkedIn: Since scraping is excluded, provide a "Manual Execution" queue where the app pops up the prospect's LinkedIn URL and copies the drafted message to the clipboard for the user to send.
- Throttle/Limits: Enforce strict daily limits on email sending and LinkedIn manual actions to protect sender reputation (e.g., max 50 actions/day).
- Email Enrichment Placeholder: Include a mock function for email enrichment (where tools like Dropcontact would go), allowing the user to manually enter missing emails.

Store all user data locally by default.
Put SMTP credentials in .env, ship .env.example.
Stop sequences immediately on reply, bounce, or manual pause.
Show deliverability warnings.
Write focused tests for the sequence logic and limit enforcement.
Create a README with setup, architecture, and backup steps.
Do not claim to reproduce proprietary data or automated inbox warm-up networks.