Can I vibecode Wrike?

Build a comprehensive, production-ready personal replacement for Wrike 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 a robust project management core loop. The system must allow a small team to plan and track projects through granular tasks, kanban boards, milestones, custom fields, threaded comments, dashboards, and a fully searchable activity history.

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 'owner', 'member', and 'viewer' roles at the project level, and rigorously test every mutation against these rules.

Core Features:
- Implement a comprehensive data model covering organizations, projects, members, issues (tasks), labels, cycles (sprints), and milestones.
- Provide polished List, Kanban, and simple Timeline (Gantt-lite) views, all backed by a single canonical issue model.
- Add robust collaboration features including rich-text comments, user mentions, task assignments, watchers, and a complete, immutable activity log tracking all changes.
- Add powerful search capabilities, CSV import and export, email notifications (via a local SMTP mock or simple integration), and automated daily database backups.
- Ship a complete `docker-compose.yml` with health checks, automated migrations, seed data for a demo workspace, and an admin recovery command.

Infrastructure & UX:
- 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 and permission logic.
- Include at least one robust end-to-end (E2E) happy-path test using Playwright or Cypress that proves the entire core loop 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 beyond local auth, billing, telemetry, analytics, or any form of a hosted control plane.
- Deliberately leave out hundreds of external integrations (no Salesforce, Jira sync, etc.).
- Deliberately leave out enterprise portfolio planning (roll-ups) and Single Sign-On (SSO).
- Deliberately leave out native mobile clients and vendor-operated uptime guarantees.

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