Can I vibecode Zoom Workplace Pro?

Build a robust, secure, and fully private personal substitute for Zoom Workplace Pro in an empty repository.
Use exactly this stack: Docker Compose, Jitsi Meet (pinned images), a small Next.js 15 control panel, PostgreSQL, and a bundled TURN server; do not offer alternative stacks.

Primary Objective: Create a self-managed, high-quality video conferencing infrastructure capable of hosting private meetings without time limits, featuring advanced administrative controls, secure room links, and strict, explicit consent for any recordings.

Detailed Feature Requirements:
1. Unrestricted Meeting Duration & Capacity: Configure the Jitsi Meet deployment to comfortably support long-running meetings (well over 40 minutes) and large groups (e.g., up to 100 participants, bounded only by the user's server hardware), effectively replacing the core Zoom Pro value proposition.
2. Advanced Admin Control Panel: Build a Next.js dashboard for the server owner to generate cryptographically signed, expiring room links. Implement a "Waiting Room" (Lobby mode) allowing the host to vet participants before admitting them.
3. Strict Recording & Storage Protocols: Cloud recording must be disabled by default. If enabled via the admin panel, it must trigger a prominent, unavoidable on-screen consent prompt for every participant. Recordings should be saved securely to a local volume or a user-defined S3 bucket, never to a third-party proprietary cloud.
4. Real-time Connection Diagnostics: Build an in-meeting diagnostic overlay showing camera/microphone status, browser capability, current bandwidth usage (up/down), packet loss, and TURN server reachability to help troubleshoot poor connections instantly.
5. In-Meeting Collaboration Tools: Ensure the deployment supports essential collaboration features including high-framerate screen sharing, in-meeting text chat, participant muting/kick controls, and basic polling.
6. Bundled Media Infrastructure: Properly configure and bundle a dedicated TURN/STUN service (like coturn) within the Docker Compose stack to ensure reliable connections across restrictive NATs and firewalls.

Strict Constraints:
- Make the first run work with one documented command. Store all metadata locally. Put secrets in `.env`.
- Do not add billing, telemetry, analytics, or a hosted control plane.
- Deliberately leave out: a global media edge network, PSTN/dial-in telephony, regulated compliance recording, and enterprise directory integrations.
- Store room metadata and audit events, but never store media streams unless explicit recording is triggered and consented to.
- Add health checks, bandwidth dashboards, backup/restore scripts, and upgrade instructions.
- Validate inputs, handle APIs gracefully, and include clear loading/error states.
- Write tests for the control panel's core logic. 
- Create a detailed README. Run tests before finishing.