Can I vibecode SeaTable Cloud?

I need you to build a comprehensive, full-stack personal replacement for SeaTable Cloud from scratch in an empty repository. The tech stack MUST be Next.js 15 (App Router), TypeScript, Tailwind CSS, PostgreSQL, Drizzle ORM, and Docker Compose. Do not suggest or use alternative stacks.

The core value proposition of SeaTable Cloud is combining the ease of a spreadsheet with the power and structure of a relational database. The core loop for this clone should allow users to model structured records, create and manage relational data across tables, and visualize this data through various customizable views.

Here are the specific features and architectural requirements:
1. Data Management: Implement workspaces, bases (databases), tables, rows (records), and columns (fields). 
2. Column Types: Support text, long text, number, currency, date, boolean (checkbox), single/multiple select, attachments (files/images), and relation fields (linking records). Include 'formula-lite' for basic calculations.
3. Dynamic Views: For any given table, support creating and saving multiple customized views:
   - Grid View: A spreadsheet-like interface with in-line editing, filtering, sorting, and grouping.
   - Kanban View: Group records into boards based on select fields.
   - Form View: Auto-generate data-entry forms based on table schema.
4. Data Operations: Support CSV import/export. Include a basic webhook system for lightweight automation when records change.
5. API: Expose a documented, token-authenticated REST API that automatically reflects the schema of bases, allowing programmatic reading/writing.
6. Local-First: Ensure user data is stored locally. The system must run independently without external cloud services.
7. Robust Engineering: Include role-based permissions, optimistic concurrency checks, an audit history log for changes, and a trash/restore mechanism.

Developer Experience & Tooling:
- Make the first run work locally with a single documented command (e.g., docker-compose up).
- Use .env for secrets, provide a .env.example, and ensure secure practices.
- Implement clear empty, loading, success, and error states. Provide robust input validation.
- Ship database migrations, seed data, backup scripts, and a schema export format.
- Write focused tests for core transformations and one end-to-end happy path.
- Produce a thorough README detailing setup, architecture, data location, and backups.

Exclusions:
- Do not add user accounts, billing, telemetry, or a hosted control plane.
- Leave out full, complex spreadsheet formula compatibility.
- Leave out third-party enterprise integrations.

Finish by running the tests to verify the setup and listing the exact commands used.