Can I vibecode ToolJet Cloud?

Build a comprehensive, production-ready personal replacement for ToolJet Cloud in an empty repository.
Use exactly this tech stack without deviation: Next.js 15 (App Router), TypeScript (strict mode), Tailwind CSS for styling, PostgreSQL for data, Drizzle ORM for database interactions, and Docker Compose for orchestration. Do not suggest or offer any alternative technologies.

Your primary objective is to recreate the core ToolJet Cloud experience: an internal tool builder. The system must allow users to define data tables and views visually, build constrained internal CRUD tools using a drag-and-drop canvas of UI widgets, connect to a single approved data source, and deploy the tool securely for a small, trusted team.

Data and Security:
- Make the first run work locally out of the box with exactly one documented command (e.g., `docker-compose up`).
- Store all user-generated data locally by default to ensure privacy and data sovereignty.
- Provide a straightforward, one-click JSON/CSV export feature so data is never trapped.
- Keep all secrets in `.env`, ship a `.env.example`, and enforce that no credentials are ever committed.
- Implement robust role-based access control (RBAC) supporting at least 'admin' and 'member' roles with strict read/write policies on a per-tool and per-data-source basis.

Core Features:
- Create a powerful schema editor supporting multiple field types: text, number, boolean, date, enum, and relational fields.
- Auto-generate UI views based on the defined schema, including list, detail, create, edit, and kanban boards.
- Develop an intuitive canvas allowing users to arrange standard UI widgets (tables, forms, charts, buttons) and bind them to queries.
- Support exactly one secure REST connector to pull external data, complete with encrypted credential storage and an explicit UI for mapping API response fields to widget properties.
- Implement a comprehensive activity log tracking all schema, data, and tool configuration changes.
- Provide robust CSV import and export capabilities for both app definitions and underlying data.
- Set up automated daily database backups and expose health check endpoints.

Infrastructure & UX:
- Ship a complete `docker-compose.yml` that stands up the app, database, runs migrations, and seeds an example workspace automatically.
- Design the UI to have meticulously crafted empty states, loading skeletons, success toasts, and highly recoverable error boundaries.
- Ensure rigorous input validation on both client and server, enforce safe filenames for any uploads, and handle unavailable APIs gracefully without crashing the frontend.

Testing & Documentation:
- Write focused, comprehensive unit tests for the core data transformations, query execution logic, and component rendering.
- Include at least one robust end-to-end (E2E) happy-path test using Playwright or Cypress that proves the entire core loop (building a tool and executing a query) functions as intended.
- Create an exhaustive README containing setup instructions, architectural diagrams/explanations, permission models, data location details, and step-by-step backup/restore procedures.

Explicit Exclusions:
- Do NOT add user accounts, billing, telemetry, analytics, or any form of a hosted control plane.
- Deliberately leave out arbitrary user-authored code execution (no eval, no custom JS script blocks).
- Deliberately leave out a broad integration marketplace or plugin system (stick to the single REST connector).
- Deliberately leave out native mobile binaries, version control for apps, and enterprise compliance features.

Finalize your work by executing the test suite and outputting the exact commands you used to verify the build.