Skip to content

ci: parity:check against cli-messaging's parity manifest - #263

Merged
leemour merged 1 commit into
mainfrom
ci/parity-check
Oct 1, 2026
Merged

leemour merged 1 commit into
mainfrom
ci/parity-check

Conversation

@leemour

@leemour leemour commented Sep 30, 2026

Copy link
Copy Markdown
Owner

Task

Parity plan P0.4, max side: CI fails on a command or option that is not in the parity manifest.

Why

tg and max are one tool with two messengers. Without a check, a command lands in one and nobody notices.

What

  • pnpm parity:check: max commands --json piped into cli-messaging-parity max, which reads parity.json from the installed cli-messaging (0.69.0).
  • CI runs it after docs:check.

Testing

pnpm build && pnpm parity:check → exit 0. The checker's own cases are tested in cli-messaging.

🤖 Generated with Claude Code

…fest

Every command and option max has must have a row in the parity.json of the
cli-messaging it installed, and every row that says max has something must be
true. A planned row passes either way.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@leemour
leemour merged commit 8f80b0b into main Oct 1, 2026
4 checks passed
@leemour
leemour deleted the ci/parity-check branch October 1, 2026 07:11
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