Can I vibecode Butter?

Build a closest honest personal substitute for the Butter (butter.us) virtual workshop and meeting tool. Use an empty repository and strictly use: Docker Compose, a custom Jitsi Meet instance for WebRTC video, Next.js 15 for the control panel and facilitation interfaces, PostgreSQL, and a TURN server. Do not offer alternative technology stacks.

The core loop involves: creating structured agendas and reusable session templates, hosting engaging facilitated workshops in private video rooms, issuing signed room invitations with expiry, and managing engagement features. Implement a lobby/waiting room where hosts admit participants, and enforce limits.

Crucially, the interface must emphasize an 'Engagement Toolkit'. Build a real-time layer on top of the video experience that includes:
- Live emoji reactions and animated sound effects.
- A managed hand-raise queue.
- Built-in live polling and Q&A blocks.
- Integrated collaboration spaces to embed Miro, Google Drive, or YouTube within the main stage without switching tabs.
- A structured, time-boxed agenda sidebar that the host advances in real-time.

For session recap, capture meeting metadata, chat logs, poll outcomes, and notes into a consolidated dashboard available after the workshop.

Make the first run work locally with one documented command. Store all user data locally with easy export. Store secrets in `.env`, include `.env.example`, and never commit credentials. Deploy Jitsi Meet using pinned Docker images.

Show connection diagnostics for participants (camera, mic, bandwidth, TURN reachability). Disable recording by default, strictly requiring on-screen consent to enable. Store room metadata, but do not store media unless requested.

Add operational features: health checks, bandwidth dashboards, backup/restore scripts, and incident instructions. Ensure the frontend includes beautiful empty, loading, success, and error states. Add input validation and graceful error handling.

Write focused automated tests for core logic (like signed links) and one end-to-end happy path for hosting a session. Create a README with setup, architecture, data locations, and backup steps.

Do not add multi-tenant accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out a global edge network, AI meeting summaries, public webinar scale, telephony dial-in, and regulated compliance features. Finish by running tests and listing the exact terminal commands used.