Can AI replace Umso?

Build a personal replacement for Umso in an empty repository.
Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export; do not offer alternative stacks.
The core loop is: assemble a clean startup landing page with a form and simple analytics, edit copy and media, preview breakpoints, and publish a static site to a user-owned target.
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.
Provide a section library for hero, proof, features, pricing, FAQ, and footer blocks.
Use a constrained design-token system rather than arbitrary CSS controls.
Allow inline text editing and local image upload with responsive optimization.
Preview desktop, tablet, and mobile widths and surface overflow errors.
Persist projects in SQLite and support a portable JSON export.
Generate a clean static Next.js output and document deployment to one target.
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 plugin marketplace.
Deliberately leave out multi-tenant managed hosting.
Deliberately leave out advanced ecommerce, memberships, and agency billing.
Finish by running the tests and listing the exact commands used.