Can AI replace Retool?

Build a personal replacement for Retool in an empty repository.
Use Next.js 15, TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks.
The core loop is: define tables and views, build one internal CRUD tool with role-aware actions over one approved trusted database, and deploy it for a small trusted team.
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 a schema editor for text, number, boolean, date, enum, and relation fields.
Generate list, detail, create, edit, and kanban views from the schema.
Implement role-based read and write rules for admin and member roles.
Support one REST connector with encrypted credentials and explicit field mapping.
Add an activity log, CSV import or export, backups, and health checks.
Ship Docker Compose with migrations and a seeded example workspace.
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 arbitrary user-authored code execution.
Deliberately leave out a broad integration marketplace.
Deliberately leave out native mobile binaries and enterprise compliance.
Finish by running the tests and listing the exact commands used.