Repository navigation
chore(deps): cli-core 0.691.0; meetings answers through meetingAnswerBody - #383
Merged
Merged
Conversation
…Body Move to @wirecat/cli-core 0.691.0 (cli-base stays 0.109.0, the peer range asks for 0.108.0 or later). The shared meetings commands now write through cli-core's meetingAnswerBody, which gets the running command as write's third argument. zm's own bodyOf wrapped the `meetings people` packet as one item with `next`, `missing` and `meta` inside it, so the paging step was hidden from an agent reading the answer's `next`. bodyOf stays for the MCP tools, the skills renderer, the inventory and the store reports. The store moves to schema 69, so the upgrade contract expects that notice (was 68). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour
added a commit
that referenced
this pull request
Nov 17, 2026
Prepares 0.80.0 so #382 (README) and #383 (cli-core 0.691.0: `meetings people` puts its next step at the top of the answer through `meetingAnswerBody`) reach npm. - `package.json`, `src/version.ts`: 0.80.0. `CHANGELOG.md`: `changes/chore-cli-core-0691.md` collected into `## 0.80.0 — 17.11.2026`, the same result as `scripts/changelog-fragments.ts` (folded by hand: the release clone had no dependencies installed). No fragments are left. ## Conformance - #383 passed CI on its branch (lint, typecheck, the full suite with coverage, docs, contracts, package checks). This branch changes only the version and the changelog. - Live check: **not run.** zm has never been run against a real Zoom account; the owner approved this release without one (NEED-2678 A, 2026-11-17), as for 0.79.0. 🤖 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 17, 2026
…op of the answer (#387) Unblocks the 0.80.0 release. Release run 44136465611 failed on all six installed-package checks (Linux, macOS, Windows × Node 22/24) at `scripts/installed-platform.mjs:456`: `TypeError: Cannot read properties of undefined (reading '0')`. Nothing was published. ## Why #383 (cli-core 0.691.0, `meetingAnswerBody`) moved `next` of `meetings people --json` from `item` to the top of the answer. The installed proof's `answer()` helper returns `packet.item`, so `people.next` became undefined. Pull request CI does not run the installed-package proof (it runs only with `pack` or on a dispatch), so #383 passed. ## What - The proof keeps the raw `meetings people` answer and reads `next` from its top level. The other reads of `next`/`meta` in the installed scripts already use the raw answer. - No changelog fragment: a release-script change, as #376. ## Testing Locally on this branch: `pnpm build`, `npm pack`, the tarball installed into a sandbox, then `node scripts/installed-platform.mjs <sandbox> 0.80.0`: the whole proof passes (Linux, Node 24.19.0), including the MCP part after the fixed line, which the failed run never reached. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task
Move zoom-cli to
@wirecat/cli-core0.691.0 and adoptmeetingAnswerBody(cli-core PR #3071).Why
zm's own
bodyOfwrapped themeetings peoplepacket as one item withnext,missingandmetainsideitem. An agent that reads the answer'snextdid not see the paging step.What
src/program-bindings.ts: the meetings deps'writeis(value, _format, command) => output(meetingAnswerBody(command, value)).bodyOfstays for its other callers (MCPtoolAnswer, skills renderer, inventory, store reports); its comment no longer names the meetings commands.>=0.108.0 <1.0.0.contracts/upgrade.jsonexpects that notice (was 68).signal(CORE-70) was already in the meetings deps (src/program-bindings.ts,signal,); no change.meetings listpaging is unchanged: probed before and after, both givepage.nexttomeetings list --page 2 --limit 1.changes/chore-cli-core-0691.mdunder "Changed — may break callers".Testing
puts the people page's next step at the top of the answerinsrc/meeting-people.test.ts: failed before the change (packet.nextundefined), passes after. The existing paging test now readsnextfrom the answer, not the item.test:coverage(762 tests), build,lint:commands,contracts:check,contracts:upgrade,generate:check,docs:check,docs:lint,test:matrix:check,security:no-leak,package:check,version:check,smoke:node,check:agent-docs: all pass.🤖 Generated with Claude Code