¿Puedo vibecodear Reply.io?

Build a closest honest personal substitute for Reply.io in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and a user-chosen transactional email provider; do not offer alternative stacks.
The core loop is: import a permissioned lead list, personalize a short compliant sequence over one email provider, enforce sending limits, and track replies without supplying proprietary contact data.
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.
Accept CSV imports only after the user confirms lawful collection and records the source.
Provide contact fields, tags, suppression status, consent notes, and a complete change history.
Build a short email sequence with delays, business-hour windows, and per-domain rate limits.
Use the configured provider for sends and process delivery, bounce, complaint, and unsubscribe webhooks.
Stop sequences immediately on reply, bounce, complaint, suppression, or manual pause.
Show deliverability warnings, daily send totals, and a mandatory preview before activation.
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.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out scraping protected platforms.
Deliberately leave out buying or generating personal contact data.
Deliberately leave out automated inbox warm-up networks and evasion of provider limits.
Finish by running the tests and listing the exact commands used.