Skip to content

chore(deps): cli-core 0.691.0; meetings answers through meetingAnswerBody - #383

Merged
leemour merged 1 commit into
mainfrom
chore/cli-core-0691
Nov 17, 2026
Merged

leemour merged 1 commit into
mainfrom
chore/cli-core-0691

Conversation

@leemour

@leemour leemour commented Nov 17, 2026

Copy link
Copy Markdown
Member

Task

Move zoom-cli to @wirecat/cli-core 0.691.0 and adopt meetingAnswerBody (cli-core PR #3071).

Why

zm's own bodyOf wrapped the meetings people packet as one item with next, missing and meta inside item. An agent that reads the answer's next did not see the paging step.

What

  • src/program-bindings.ts: the meetings deps' write is (value, _format, command) => output(meetingAnswerBody(command, value)). bodyOf stays for its other callers (MCP toolAnswer, skills renderer, inventory, store reports); its comment no longer names the meetings commands.
  • cli-core 0.687.0 → 0.691.0. cli-base stays 0.109.0: cli-core's peer range is >=0.108.0 <1.0.0.
  • Store schema 69 (cli-core 0.689.0): contracts/upgrade.json expects that notice (was 68).
  • The run's stop signal (CORE-70) was already in the meetings deps (src/program-bindings.ts, signal,); no change.
  • meetings list paging is unchanged: probed before and after, both give page.next to meetings list --page 2 --limit 1.
  • Changelog fragment changes/chore-cli-core-0691.md under "Changed — may break callers".

Testing

  • New test puts the people page's next step at the top of the answer in src/meeting-people.test.ts: failed before the change (packet.next undefined), passes after. The existing paging test now reads next from the answer, not the item.
  • Local: standards, lint, typecheck, 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

…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
leemour merged commit d58ae66 into main Nov 17, 2026
11 checks passed
@leemour
leemour deleted the chore/cli-core-0691 branch November 17, 2026 16:07
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>
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