- Shipped
- 29 மார்ச், 2026 அன்று 4:17 PM UTC
- Author
- kamo
- Commit
- bf7286d
ROOT CAUSE: The OTK had a 10-second TTL. By the time the kamo-meet page loaded all its assets and branding/overrides.js ran to validate the OTK, it had already expired in Redis → 401 → no session → no name → no JWT → 'Waiting for moderator'. Fixes: - Meet OTKs now get 60s TTL via ?purpose=meet parameter - Chat invites run independently (not after backend meeting creation) - Email invites run independently - Backend meeting record creation is fire-and-forget (doesn't block)