Can I vibecode Unbounce?

Build a highly functional clone of Unbounce, focusing on its core conversion rate optimization and landing page builder capabilities. The application should be built in an empty repository using Next.js 15, TypeScript, Tailwind CSS, SQLite, and Drizzle ORM. The primary focus is enabling marketers to quickly build, test, and optimize landing pages.

### Core Features to Implement:

1. **Visual Drag-and-Drop Page Builder**: Create an intuitive, visual editor allowing users to assemble landing pages without writing code. Provide customizable templates for common scenarios (SaaS, Lead Gen). The builder should support previewing across desktop, tablet, and mobile breakpoints to ensure responsive design. Allow users to inject custom CSS and JavaScript for advanced customization. Include a section library with Heroes, Pricing, Features, FAQs, Footers, Popups, and Sticky Bars. 

2. **A/B Testing Framework**: Build a native A/B testing tool. Users should be able to create variations of a landing page (Variant A, Variant B), split traffic between them, and track metrics like page views and button clicks to declare a winning variant. This is critical to replicate Unbounce's CRO value.

3. **Dynamic Text Replacement (DTR)**: Implement a dynamic text replacement engine. The landing page should be able to parse URL parameters (e.g., `?utm_term=software`) and dynamically inject these terms into the page's headings or paragraphs. This mimics Unbounce's ability to match ad copy with landing page copy for higher relevance.

4. **AI-Assisted Layouts**: Integrate a basic generator that can suggest structural layouts or generate placeholder copy based on a prompt to mimic the Unbounce Smart Builder.

### Technical & Architecture Requirements:

- **Local First & Persistence**: The app must run locally with one documented command. Store all project data (pages, variants, components) locally using SQLite and Drizzle ORM. Provide a straightforward mechanism to export projects as portable JSON files.
- **Static Export**: The platform must generate clean, static Next.js outputs for the landing pages, enabling users to easily deploy them to their own targets.
- **Quality & Security**: Store configuration in `.env` (ship `.env.example`). Include comprehensive loading, success, and error states. Ensure robust input validation.
- **Testing**: Write focused tests for the A/B testing logic and DTR engine, plus an E2E test for the core page builder loop.

### Exclusions:
Deliberately exclude multi-tenant managed hosting, billing/subscriptions, plugin marketplaces, and advanced e-commerce. Focus strictly on the standalone page building and optimization flow. Provide a comprehensive README with setup, architecture, and deployment steps.