Can AI replace Pestle?

Build a personal replacement for Pestle in an empty repository.
Use Next.js 15, TypeScript, SQLite, Drizzle ORM, and a local-first PWA; do not offer alternative stacks.
The core loop is: save recipes, guide cooking steps, plan meals, share or print a household shopping list, and keep data portable and owner-controlled.
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.
Create household members, shared lists, calendar items, recipes or inventory records, and assignments.
Provide fast mobile-first capture with large controls, offline queueing, and conflict-safe sync to one server.
Support recurring chores or events, reminders, completion history, and printable views.
Add CSV or JSON import and export plus photo attachments with clear size limits.
Allow private and shared items and make every change attributable and undoable.
Add backups, household export, member removal, and a simple invite code.
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 retailer ordering and proprietary product catalogs.
Deliberately leave out broad smart-home integrations.
Deliberately leave out large public recipe libraries and polished native mobile clients.
Finish by running the tests and listing the exact commands used.