Can I vibecode Crowdcast?

Build a comprehensive personal substitute for Crowdcast, focusing on interactive live streaming and community engagement. You will build this in an empty repository using Next.js (App Router), Tailwind CSS for styling, PostgreSQL (via Prisma or Drizzle), WebRTC for video, and WebSockets (Socket.io or PartyKit) for real-time interactions.

Core Features & App Workflow:
1. Event Management & Landing Pages: Create an owner dashboard to schedule upcoming live events. Each event should have a dedicated, customizable registration page where users can RSVP. Include support for multi-session events, where one event can have multiple distinct broadcasts (sessions) with their own separate chats and Q&A.
2. Live Streaming Interface & Stage: Build a clean, modern broadcast interface. The host should be able to broadcast video and share their screen. Implement a "Stage" feature allowing the host to invite up to three audience members to turn on their cameras and join the live broadcast (like going on stage).
3. Real-Time Chat & Timestamped Comments: Implement a sidebar live chat for real-time audience interaction. Add the ability for viewers to leave timestamped comments that link to specific moments in the broadcast, making replays highly navigational.
4. Interactive Q&A: Build a dedicated Q&A tab. Audience members should be able to submit questions, upvote existing questions, and the host should have moderation tools to highlight the current question being answered on-screen.
5. Live Polls & Calls to Action (CTAs): Enable the host to create and trigger polls in real-time, showing live results to the audience. Also, add the ability to push custom CTAs (e.g., buttons linking to external resources) during the stream.
6. Replays & Analytics: Automatically record sessions and make them available as replays. Provide an analytics dashboard for the host showing attendee counts, chat engagement, poll results, and CTA clicks. Add simple export functionality (CSV) for attendee data.

Technical Requirements:
- Use Docker Compose for easy local development, wrapping the database, frontend, and real-time services.
- Provide a clear, one-command setup (e.g., `docker compose up`) to run the entire stack locally.
- Use WebRTC (or a wrapper like LiveKit or simple-peer if preferred, but keep it self-hostable) for the core video broadcast.
- The chat, Q&A, and polls must be real-time, utilizing WebSockets for instant updates across all connected clients.
- Implement clear empty states, loading indicators, and graceful error handling.
- Write a comprehensive README with setup instructions, architecture overview, and deployment guidelines.
- Add an environment variables template (.env.example) and ensure secrets are securely handled.

Out of Scope:
- Do not build complex paid ticketing or billing systems (assume free access for this clone).
- Do not build a global edge network for scaling to tens of thousands of viewers. The focus is on the core interactive features for a small to medium-sized audience.
- Leave out third-party integrations (like Zapier, Mailchimp) for now.

Finish by providing the directory structure and the command to initialize the project, followed by implementing the core data models and the main live event interface components.