chore(parity): update manifest to reflect 2026-05-05 CLI merges#42
Closed
mikemolinet wants to merge 1 commit into
Closed
chore(parity): update manifest to reflect 2026-05-05 CLI merges#42mikemolinet wants to merge 1 commit into
mikemolinet wants to merge 1 commit into
Conversation
Today's merged work brings the CLI to 100% coverage of the hosted API's merged endpoints. Updates the manifest accordingly: - Bump `last_full_audit` to 2026-05-05, `cli_version_at_audit` to 0.2.0 - Add 19 new commands to `commands_covered`: - executions: replay, verify, verification-pending (#31) - workers: list, delete (#33) - key webhook-secret: get, regenerate (#33) - agents: create, list, get, update, delete, inbox, sent, webhook-secret get/regenerate (#28) - messages: send, get, read, ack (#29) - Expanded existing entries to enumerate the new flags from #26 + #27 + #30 (e.g. executions list now lists --outcome-state / --result-type / --has-evidence / --triggered-by). - Empty `endpoints_missing` and `command_drift` — every prior gap was closed by today's merges. - Add 8 entries to `ported_pr_history` covering #26, #27, #28, #29, #30, #31, #33 (and the §17 BCC-light port via #29). - Add new `open_ports_in_flight` section tracking cueapi-cli #40 (message-to + online-only + describe) and #41 (--mode flag for Surface 6 v2 delivery_mode), so they don't show as missing in the next audit and have a clear "promote to commands_covered when merged" hook. - Update `notes` to flag what the next audit should pick up: Surface 1 (last_seen_at, cueapi #630 in-flight) + the Surface 6 v2 server-side bridge. Pre-staged per the parity-manifest sequencing risk: the manifest only references work that has already merged on cueapi-cli main, so the diff is safe to land independently and doesn't claim coverage that doesn't exist yet. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
Author
|
Closing as superseded — this duplicates the pre-existing PR #38 ( |
auto-merge was automatically disabled
May 5, 2026 21:45
Pull request was closed
mikemolinet
added a commit
that referenced
this pull request
May 12, 2026
…ity) (#54) Server-side Item 1 (hosted PR #791) added `subscriptions.inline_body` opt-in body embedding for pull subscriptions — when True, the source message body is embedded in the event payload as `payload.body`, eliminating the extra GET /v1/messages/{id} round-trip on the consumer side. This CLI port wires the kwarg through `subscriptions create` via a new `--inline-body` click flag (is_flag, defaults False). When omitted, the field is NOT sent on the wire — preserves pre-#791 wire format for the common no-embed case. When set, sends `inline_body: true` in the JSON body. Companion to cueapi-python PR #42 (SDK `inline_body` kwarg on `AgentsResource.subscriptions_create`). Same semantic, same default- omit behavior. Mirrors the existing pattern in cueapi-cli where default-omit avoids payload noise for unopted callers. Tests (3 new): - test_subscriptions_create_inline_body_flag_default_omits_field — no flag = no field on wire - test_subscriptions_create_inline_body_flag_opts_in — --inline-body sends true - test_subscriptions_create_help_lists_inline_body — --help mentions the flag + the 32KB cap Backlog row: cmp1v3azw.
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
1 participant
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.
Summary
Refresh `parity-manifest.json` so it reflects the seven CLI ports that merged today (#26, #27, #28, #29, #30, #31, #33). The CLI is now at 100% coverage of all merged hosted-side endpoints — every entry in `endpoints_missing` was closed by today's work.
cueapi executions replay / verify / verification-pending#31)cueapi workers list/delete+cueapi key webhook-secret get/regenerate#33)cueapi workers list/delete+cueapi key webhook-secret get/regenerate#33)cueapi agentscommand group (messaging primitive — identity + inbox + sent) #28)cueapi messagescommand group (messaging primitive — message lifecycle) #29)cueapi agentscommand group (messaging primitive — identity + inbox + sent) #28, feat: addcueapi messagescommand group (messaging primitive — message lifecycle) #29, feat: add remaining create + update flags (delivery, alerts, catch-up, verification, on-success-fire, status) #30, feat: addcueapi executions replay / verify / verification-pending#31, feat: addcueapi workers list/delete+cueapi key webhook-secret get/regenerate#33 (and the §17 BCC-light port via feat: addcueapi messagescommand group (messaging primitive — message lifecycle) #29).Sequencing safety
Pre-staged per the parity-manifest sequencing risk: this PR only references work that has already merged on cueapi-cli main, so the diff is safe to land independently and doesn't claim coverage that doesn't exist yet. The two in-flight PRs (#40 + #41) live in `open_ports_in_flight` rather than `commands_covered` for that reason.
Test plan
🤖 Generated with Claude Code