Skip to content

fix(parity): known-broken lists only whatsapp-cli; rows for messages scheduled cancel|edit|send - #3146

Merged
leemour merged 2 commits into
mainfrom
fix/parity-core-0707
Nov 19, 2026
Merged

leemour merged 2 commits into
mainfrom
fix/parity-core-0707

Conversation

@leemour

@leemour leemour commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Task

scripts/parity/known-broken.json should list only CLIs that are really broken, each with a reason. The 0.707.0 release run (44463906253) shows most of the list passes.

What changes

CLI Before Now Evidence
mail-cli, cli-memo, tg-cli, gcal-cli (both entries), bitrix24-cli listed (#2896, #2903) removed the run's "passes; remove it" warnings
cli-template listed (#2896) removed its tests pass in the run's template job
max-cli listed (#2896) stays until 2026-11-21, re-pointed to this PR fixed in WireCatLabs/max-cli#984, but max's own CI runs the parity manifest check against cli-core on npm, so #984 merges only after a release carries the rows below. Until then a release builds max's main, which still fails
drive-cli listed (#2896) removed fixed in WireCatLabs/drive-cli#384
zoom-cli listed (#2896) removed fixed in WireCatLabs/zoom-cli#389
whatsapp-cli listed (#2896) stays, re-pointed to #3139 with a reason its messenger.test.ts fails: #3139 added cancelScheduled, editScheduled, sendScheduled to COMMAND_NEEDS, and WHATSAPP.lacks does not name them yet

An entry now has a reason field; the scripts read only repo and until, so nothing else changes. The error message asks for the reason too.

A gap this uncovered: parity.json rows

#3139 added messages scheduled cancel|edit|send without parity.json rows. The manifest check (main (max), main (tg)) failed in the release run, but continue-on-error hid it because both CLIs were listed. Removing them without the rows would make the release gate fail. The rows say: in max and tg, not in wa ("WhatsApp has no scheduled messages"); --html on edit in tg only, as on messages edit. docs/dev/STANDARD.md re-rendered.

Testing

  • The parity check against the release run's own commands.json artifacts: tg, max, wa and wording pass with the new rows; tg and max failed before them.
  • pnpm vitest run src/parity (53 tests), pnpm docs:check.
  • This branch is named like the CLI pull requests, so this PR's parity builds max-cli, drive-cli and zoom-cli from their fix branches (app-ref.sh). A PR's parity runs no CLI tests; those ran locally in each CLI and run at the next release.

Merge freely: max-cli stays listed, and zoom-cli and drive-cli merge on their own green CI. The release after this one should run with --app-ref fix/parity-core-0707 so parity builds max-cli from its fix branch.

🤖 Generated with Claude Code

leemour and others added 2 commits November 19, 2026 08:44
…scheduled cancel|edit|send

The 0.707.0 release run (44463906253) reported mail-cli, cli-memo, tg-cli, gcal-cli and
bitrix24-cli as passing, and cli-template's tests passed. max-cli, drive-cli and zoom-cli are
fixed in their own pull requests. whatsapp-cli stays, re-pointed to #3139 with its reason.

#3139 added three messages scheduled commands without parity.json rows, so the manifest check
failed for max-cli and tg-cli; continue-on-error hid it while both were listed. A known-broken
entry now carries a reason, and the error message asks for one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
max-cli#984's own CI runs the parity manifest check against cli-core on npm, which has no
messages scheduled rows yet, so it cannot merge before a release carries them. A cli-core release
in between would build max-cli's main, which still fails. The entry ends on 2026-11-21.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit 66e4b66 into main Nov 19, 2026
44 checks passed
@leemour
leemour deleted the fix/parity-core-0707 branch November 19, 2026 10:19
leemour added a commit that referenced this pull request Nov 20, 2026
## Task

`scripts/parity/known-broken.json` should list only CLIs that are really
broken. #3146 kept max-cli there until its parity.json rows reached npm,
because max-cli#984 could not pass its own parity check before that.

## What

- max-cli#984 is merged on cli-core 0.714.0, with green CI
(`parity:check`, tests, smoke, contracts). Its entry is removed.
- whatsapp-cli stays (#3139, until 2026-11-26): `WHATSAPP.lacks` does
not name `cancelScheduled`, `editScheduled` and `sendScheduled` yet.
- Changelog fragment. No release: the next regular one carries it.

## Testing

`pnpm docs:check`; this PR's parity builds max-cli main against this
checkout.

🤖 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