Can I vibecode Zencal?

Build a monetization-focused scheduling platform as a personal replacement for Zencal.
Use exactly this stack: Next.js 15 (App Router) + TypeScript + PostgreSQL + Drizzle ORM + TailwindCSS + Stripe (mocked or real).
Primary job: Build a scheduling tool specialized for freelancers and coaches to publish booking pages, collect optional payments, and manage availability.

Core Features & Requirements:
1. Paid Meetings & Monetization:
- Implement a booking flow that allows the host to attach a price to specific meeting types.
- Integrate a payment step (using Stripe Checkout or a simulated mock payment gateway) before finalizing the booking.
- Support configurations for one-off payments and "free for free" meetings.

2. Branded Booking Pages:
- Create customizable profile pages that act as a standalone landing page for the host.
- Include sections for a brand logo, custom accent colors, service descriptions, pricing tiers, and client reviews (testimonials).
- Ensure the layout is highly professional and conversion-optimized.

3. Availability & Calendar Sync:
- Read one calendar, publish availability, create conflict-safe bookings, and send confirmations.
- Implement configurable working hours, buffer times between meetings, minimum notice periods, and booking horizons.
- Calculate availability in UTC and render it correctly in the visitor's detected timezone.

4. Technical & Architecture Constraints:
- Make the first run work locally with one documented command (e.g., Docker compose for Postgres).
- Store all user data locally by default and make export straightforward.
- Put secrets in .env, ship .env.example, and never commit credentials.
- Add an admin booking list, event-type editor, audit log, and calendar reconnect flow.
- Include clear empty, loading, success, and recoverable error states.

5. Exclusions & Limitations:
- Do not add accounts, billing for the SaaS itself, telemetry, analytics, or a hosted control plane.
- Deliberately leave out Microsoft/Apple calendar support and complex team round-robin routing.
- Do not fake compliance or security claims.
- Handle unavailable APIs (like the payment gateway) gracefully.

6. Testing & Documentation:
- Write focused unit tests for timezone calculations and pricing logic.
- Add one end-to-end happy path test for a paid booking.
- Create a README with setup, architecture, permissions, data location, and backup steps.
- Finish by running the tests and listing the exact commands used.