Common Lifecycle Pattern

1. Initialize Prober / Reporter.
2. Request media permissions and enumerate devices.
3. Run targeted diagnostics (diagnoseAudio, diagnoseVideo).
4. Run comprehensive network diagnostic (startToDiagnose) and stream stats to UI.
5. Produce final report and apply readiness gates.
6. Stop/cleanup (stopToDiagnose, stopToDiagnoseVideo, releaseMediaStream, cleanup).

High-Level Scenarios

• Pre-join diagnostics page before Meeting SDK join action.
• Support workflow that captures structured report for customer troubleshooting.
• Device certification flow for kiosk or controlled endpoint environments.
• Browser capability gating for advanced media features.

See scenarios/high-level-scenarios.md for details.

Chaining

• Meeting pre-join gate: ../meeting-sdk/web/SKILL.md
• Video session readiness gate: ../video-sdk/web/SKILL.md
• Telemetry/report ingestion backend: ../rivet-sdk/SKILL.md + ../rest-api/SKILL.md

Environment Variables

• See references/environment-variables.md for optional .env keys and how to source values.

Operations

• RUNBOOK.md - 5-minute preflight and debugging checklist.