zoom: require Client Secret with Client ID (1.0.2)

[staugaard]

Almost all Zoom sign-in failures we see are invalid_client from a blank Client Secret. The current form calls the secret optional, so people paste a regular Client ID and leave the secret empty.

This makes the copy lead with the Client Secret being required along with the Client ID, and keeps the Public Client ID as the no-secret option.

• CLIENT_ID and CLIENT_SECRET titles and descriptions updated
• README setup steps put Client ID + Secret first
• Version bumped to 1.0.2 with a CHANGELOG entry
• Variable keys, required and mcp.json are unchanged

The marketplace listing picks this up on the next Reindex Repo for cursor/plugins.

---

Note

Low Risk
Documentation and plugin marketplace copy only; no runtime auth or MCP configuration changes.

Overview
Bumps the Zoom Cursor plugin to 1.0.2 and rewrites setup copy so admins stop pairing a confidential Client ID with an empty secret (which triggers Zoom invalid_client at token exchange).

Plugin config UI (plugin.json): retitles the credential fields to Zoom Client ID or Public Client ID and Zoom Client Secret (needed with the Client ID), and updates descriptions to state the secret is required with a regular Client ID while Public Client ID remains the PKCE/no-secret path.

README reorders setup to present Client ID + Secret first, Public Client ID as the alternative, adds a note to re-enter the secret after Zoom regeneration, and tightens install/team wording around “credentials” instead of only client ID.

CHANGELOG documents the above; variable keys, required fields, and mcp.json auth wiring are unchanged.

^{Reviewed by Cursor Bugbot for commit 9c1de27. Bugbot is set up for automated code reviews on this repo. Configure here.}