Mission 3 · Zoom integration
Prove the meeting adapter in simulation before live credentials.
Validate a synthetic Zoom response and mock CRM reconciliation first, then optionally configure a least-privilege account path, create a controlled meeting, and write the join URL only after read-back.
Build sequence
- Run the supplied no-network adapter simulator and verify provider ID, correlation ID, item ID, safe URL domain, and mock CRM read-back.
- Reject a mismatched item, unsupported provider state, or non-test URL before any write-back.
- For an optional live lane, verify account tier, licensed host, app type, scopes, and meeting owner before storing credentials.
- Keep account and app secrets only in private runtime configuration and exclude them from Git, Moodle, logs, and proof media.
- Create a controlled live test meeting only when eligible, then write the participant URL and Link ready state after exact read-back.
- Run an invalid-credential or insufficient-scope negative in the live lane, or an equivalent simulator failure when live access is unavailable.
Required proof
- Simulator self-test, synthetic provider response, and exact mock CRM reconciliation.
- Sanitized capability preflight plus meeting ID suffix or hash, never a secret or full private join record.
- Negative fixture and read-back proving URL and state belong to the intended synthetic item.
Reference files and sources
Official vendor documentation
Assessment gate
Pass
Pass: simulator reconciliation and failure checks pass; any live lane also proves least privilege, secret isolation, meeting creation, and exact read-back.
Revise
Revise: the adapter path works but simulation, capability checks, scope evidence, failure handling, or read-back is weak.
Hard fail
Hard fail: credentials, private participant data, or an unverified link is exposed.
Human-reviewed submission
