Skip to content

feat(meetings)!: read Zoom through cli-core's find/get, manage meetings under meetings, drop remote-meetings - #373

Merged
leemour merged 5 commits into
mainfrom
feat/meetings-find-get-management
Nov 15, 2026
Merged

leemour merged 5 commits into
mainfrom
feat/meetings-find-get-management

Conversation

@leemour

@leemour leemour commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

Task

gcal's cross-CLI parity check fails on zoom. zm's meetings update linked a stored meeting to an event, while cli-core's shared meetings update changes a meeting on the service. zoom was also still on cli-core 0.663.0. The owner ruled: move zoom to cli-core 0.667.0, move the event link off meetings update with no alias, and adopt cli-core's meeting reads and management.

What

  • Dependencies: cli-core 0.667.0 (was 0.663.0), cli-base 0.102.1 (was 0.100.0). With cli-base 0.102.1, --json <fields> keeps the untrusted list.
  • Live reads: ZoomApiSource implements find, get and finds. meetings list finds meetings that ran and are not stored yet. meetings show reads one again by its instance uuid or its meeting number (then its latest instance).
    • Sync, find and get all name a run by its instance uuid (cli-core's "one meeting, one id").
    • finds.upcoming is false, because Zoom gives each run its own uuid.
    • get needs the optional meeting:read:past_meeting scope (added to the app guide), and refuses with permission_error without it.
    • get writes no series, because a past meeting's answer has no join link or recurrence.
  • Bounded live list: find asks List meetings with from/to (whole UTC days, timezone=UTC), type=previous_meetings and page_size=300, one 30-day stretch of the started_at window per call, newest first. Past instances get the same from/to. A call reads the runs of at most 20 series, and its cursor carries on in the same page, then in the stretch before. One list sends at most 3 calls × 2 pages × 21 = 126 requests; a plain list sends at most 42.
    • With no started_at, the list starts at today and walks back to Zoom's 6-month limit. When cli-core's page cap stops it first, the answer is complete: false with meetings.server-capped.
    • Upcoming meetings stay out (finds.upcoming: false): one that has not run has no instance uuid to store. cli-core says so in missing, and meetings scheduled lists them.
    • Not run against real Zoom: the from, to, timezone and page_size parameters follow Zoom's List meetings docs. The tests use a strict fake: it refuses from without to, a date that is not a day, no timezone, and a page over 300.
  • Management: meetings create|update|cancel|invitation come from cli-core's createMeetingManagement.
    • A create needs --start-time. There is no instant meeting.
    • zm asks first once, after validation, as the profile's permission says.
    • These commands open no store and need no login for a preview.
  • Removed: remote-meetings, with no alias.
  • Renamed: meetings update <ref> --event-id → meetings link <ref> --event-id. link already carried the person link.
  • Docs: docs/remote-meetings.md → docs/meeting-management.md. The other pages, the skill and the generated references are updated. The changelog note is changes/feat-meetings-find-get-management.md.

A fresh review agent found three bugs, all fixed here, each with a regression test:

  • The configured source called find/get without binding them to their object, so live reads never ran.
  • get blanked the stored series.
  • The changelog did not mention the --dry-run change.

Testing

  • Locally: the full suite passes (751 tests), with typecheck, biome, docs:check, contracts:check and pnpm generate. The test matrix shows 344 tested, 21 untested with a reason, 0 missing.
  • New tests:
    • the same id from sync, find and get;
    • requests per find page;
    • the missing scope;
    • a series-less get;
    • live reads through the configured source;
    • refused kind, start and settings without asking;
    • a saved remote-meetings key;
    • untrusted marks under --json=<field> in a locked run.

🤖 Generated with Claude Code

leemour and others added 5 commits November 15, 2026 10:02
…gs under `meetings`, drop remote-meetings

- cli-core 0.667.0 (was 0.663.0) and cli-base 0.102.1 (was 0.100.0).
- ZoomApiSource implements find/get: `meetings list` finds meetings that ran and are not stored, and
  `meetings show` reads one again from Zoom by its instance uuid or its meeting number (then its latest
  instance). Sync, find and get name a run by the same instance uuid. get needs the optional
  meeting:read:past_meeting scope, refuses with permission_error without it, and writes no series,
  since a past meeting's answer has no join link or recurrence. finds.upcoming is false: Zoom gives each
  run its own uuid.
- meetings create|update|cancel|invitation come from cli-core's createMeetingManagement; a create needs
  --start-time, there is no instant meeting. They open no store and need no login for a preview.
- remote-meetings is removed, with no alias. Its permission default is gone; cli-core asks first for
  meetings.create|update|cancel.
- The stored-event link moves from `meetings update --event-id` to `meetings link --event-id`, so
  `meetings update` means the same as in every other CLI on cli-core.
- docs/remote-meetings.md becomes docs/meeting-management.md; the other pages, the skill and the
  generated references follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…onth at a time

`meetings list` sent one previous-meetings page of up to 100 series and one instance request per series,
with no dates: up to ~600 requests per list.

- find asks List meetings with from/to (whole UTC days, timezone=UTC) and page_size=300, one 30-day
  stretch of the started_at window per call, newest first; past instances get the same from/to.
- At most 20 series' instances per call; the cursor carries on in the same page, then the stretch
  before. One list sends at most 3 calls x 2 pages x 21 = 126 requests.
- Without started_at it starts at today and walks back to Zoom's 6-month limit; when cli-core's page
  cap stops it first, the answer is complete: false with meetings.server-capped.
- Tests use a strict fake that refuses from without to, a non-day date, no timezone or a page over 300.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…Info

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ew paths

The ci check failed its 97% statement floor (96.52%): the removed remote-meetings tests had covered
code that is now unused or untested.

- ZoomRemoteMeetings.list/show and the management list/get ports are gone: no command calls them.
- checkPermission no longer asks: no zm command takes its own --yes now; cli-core's management asks
  through askBeforeWrite.
- The configured source declares find/get without stand-in functions, and calls the built source's
  method on it.
- Tests: link's mixed event and person forms, a bad find cursor, an invalid list, a repeated token,
  an empty id, a meeting that never started, a transcript refusal, a folder source and reset, and a
  malformed provider answer. Statements 97.03% locally.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- meetings update, cancel and invitation get examples that name the meeting.
- meetings link's summary fits 80 characters.
- "meetings invitation" is cli-core's word, so it joins the unknown-verb baseline; the stale
  "search meetings --tag" option-role entry is gone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit 55a017a into main Nov 15, 2026
11 checks passed
@leemour
leemour deleted the feat/meetings-find-get-management branch November 15, 2026 20:13
@leemour leemour mentioned this pull request Nov 15, 2026
leemour added a commit that referenced this pull request Nov 15, 2026
## Task
Release #373 (cli-core 0.667.0, find/get, management under `meetings`,
`remote-meetings` removed, the event link moved to `meetings link
--event-id`).

## What
`changes/feat-meetings-find-get-management.md` is collected into `##
0.77.0 — 15.11.2026`, and the version is raised to 0.77.0 in
`package.json` and `src/version.ts`.

## Testing
`pnpm version:check` and `pnpm docs:check` pass locally.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
leemour added a commit that referenced this pull request Nov 15, 2026
…ts with meetings link (#376)

## Task
The 0.77.0 release ([run
43757122355](https://github.com/WireCatLabs/zoom-cli/actions/runs/43757122355))
failed `installed-platforms` on all six jobs with "network, browser or
keyring accessed". Nothing was published.

## What
- `scripts/installed-platform.mjs`: `meetings list` and `meetings show`
now also ask Zoom (#373), so they read the keyring, which the proof
forbids. The proof's store reads now pass `--backend archive`, both from
the CLI and in the MCP `zm_read` calls.
- `scripts/installed-meeting-integration.mjs`: event links use `meetings
link --event-id`, which #373 missed.

## Testing
The installed-platform proof passes locally on Linux (Node 24.19.0)
against the packed 0.77.0 tarball. Typecheck and biome pass. The
platform jobs run only on a release, so the release run checks Windows
and macOS.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant