docs: say who can connect an unpublished Zoom app, and what to do otherwise

[distronode-com]

Answers #35.

What was wrong. Settings → Zoom, step 2, said the Zoom app can stay unpublished because "your own team's Zoom users can still connect". In Calnode, "team" reads as the people on the Members page, and that is not what Zoom allows. An unpublished General app can only be authorized by users inside the Zoom account that created it (Zoom: sharing private and beta apps: "You can only share private apps with members within your Zoom account"). A member who connects with their own Zoom account is turned away on marketplace.zoom.us/error ("Something went wrong", the screenshot in #35) before /v1/zoom/callback is ever called, so Calnode never sees the failure and cannot explain it at the moment it happens.

What this changes. Docs and one sentence of UI text, no behaviour:

• Settings → Zoom step 2 now says who can connect an unpublished app, and points at the deploy guide for the rest.
• DEPLOY.md gains §8 Zoom meeting links: the account rule; Zoom's three ways past it (bring hosts into the app's Zoom account, beta sharing with Zoom's stated limits of 100 users and 4 weeks plus two extensions, or publishing) with links to Zoom's docs; and the fallback that needs no Zoom app, a Zoom link on the event type, which mintMeetingLink already uses whenever the primary host has not connected Zoom. It says plainly that this is one link per event type, so it suits a personal room better than a rotation, and that the built-in video rooms (§7) need no per-host account.
• A troubleshooting row for the symptom. First run and Troubleshooting become §9 and §10; nothing in the repo referred to them by number.
• A CHANGELOG entry.

What it does not do. It does not try to detect the refusal: Zoom handles it on its own domain and never redirects back.

Checked: pnpm check and pnpm build pass; go build ./... passes.

🤖 Generated with Claude Code

[pullfrog]

✅ No new issues found.

Reviewed changes Docs and one Settings → Zoom sentence that correct who can authorize an unpublished Zoom app, plus the static-link fallback.

• Settings → Zoom step 2 now states Zoom's same-account rule for unpublished General apps instead of "your own team," and points at DEPLOY.md.
• DEPLOY.md §8 documents that rule, Zoom's three workarounds (same account, beta sharing, publish), the event-type Zoom-link fallback mintMeetingLink already uses, and a troubleshooting row for the Marketplace error; First run / Troubleshooting become §9 / §10.
• Changelog Unreleased/Fixed entry pointing at #35.

  ^{｜ View workflow run ｜ Using Grok ｜ 𝕏}

[shockalotti]

Approved. Docs-only, and it corrects a claim that was actively sending members into a dead end Zoom never reports back to us. The three workarounds are Zoom's, accurately hedged (beta sharing framed as a test channel, same-account framed with the admin/licensing cost), plus the link-only fallback and the new troubleshooting row. No behavior touched.