Can I vibecode Stackby?

Build a personal replacement for Stackby in an empty repository, focusing on combining spreadsheet usability with automated API data fetching.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Docker Compose; do not offer alternative stacks.
The core loop is: build a small table-based operational tracker with structured records, provide grid, form, and kanban views, and allow specific columns to fetch and map data from external REST APIs automatically.
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 UI for workspaces, bases, and tables. Support text, number, date, boolean, and basic formula field types.
Crucially, implement an "API Column" type: a field that can be configured with an external API endpoint (e.g., YouTube API to fetch video views, or a generic GET request), map the JSON response to other columns in the same row, and provide a manual "refresh" button for the row.
Build grid and record-detail views from one canonical schema. Add role-based permissions, optimistic concurrency checks, and basic audit history.
Provide CSV import/export and a token-authenticated REST API generated from the user's schema.
Ship migrations, seed data, backups, and a schema export format. Include clear empty, loading, success, and recoverable error states.
Write focused tests for the core API-fetching and data transformation logic.
Create a README with setup, architecture, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out full spreadsheet formula compatibility, hundreds of native 3rd-party integrations, and team collaboration features.
Finish by running the tests and listing the exact commands used.