Zoom: Apache Software Foundation (ASF) meetings fail to admit bot — org-policy admission flow not handled

[DmitriyG228]

Symptom

Vexa bot fails to join Zoom meetings hosted by the Apache Software Foundation. ASF runs Zoom under organizational policy that includes registration-required attendee flow, attendee-info forms, and community-confidential meeting metadata gates. The current Zoom Web path does not navigate this admission flow.

Repro

• Use any ASF-hosted Zoom meeting link (e.g. an ASF project working group meeting).
• Dispatch a Vexa bot via standard `POST /bots` flow.
• Observe: bot does not reach `active`; admission stalls or fails.

Expected

• Bot recognizes the ASF / org-policy admission DOM (registration form, attendee info gate).
• Either:
  • Provides a path to fill the registration form from supplied bot identity, or
  • Fast-fails with a classified reason (e.g. `zoom_org_policy_registration_required`) so callers can switch to a Meeting-SDK-backed path or skip the meeting.

Notes

• Distinct DOM/admission flow from the consumer Zoom Web path covered by Zoom Web per-speaker pipeline broken on modern Zoom client: bot scrapes <audio>.srcObject DOM elements that no longer exist — 0 transcripts on real meetings (confirmed live mid 11717) #318.
• May be unblocked by epic: Zoom Meeting SDK recovery — finish + ship the native track #253 (Zoom Meeting SDK recovery) instead of fixing the Web path; worth deciding before investing.
• Likely benefits from the same detection + classified-failure pattern requested in GMeet rejection page silently times out instead of fast-failing — bot waits 120s on hidden name input + no retry policy for transient host-not-started case #316 / sibling Zoom `host_busy` issue.
• Source: groom round 2026-05-08 (post-v0.10.6).