feat: port cueapi PR #589 + #590 to MCP tools

[mikemolinet]

Summary

Closes 2 entries from endpoints_missing / tool_param_drift in cueapi-mcp #13's parity-manifest.json. Companion to cueapi-cli #26 (already merged 2026-05-04 17:57-17:59 UTC).

PR #589 — effective payload on GET responses

cueapi_get_execution and cueapi_list_executions are passthrough handlers, so the new payload field surfaces automatically. Tool descriptions updated so MCP hosts know the field exists.

PR #590 — server-side payload_override enforcement

Two new optional fields on cueapi_create_cue + cueapi_update_cue:

Field	Type	Behavior
require_payload_override	bool	Reject fires without payload_override (HTTP 400 payload_override_required)
required_payload_keys	string[]	Required keys in resolved post-merge payload (HTTP 400 missing_required_payload_keys + missing_keys list)

cueapi_fire_cue description surfaces all 3 new server error codes (the third being inconsistent_message_instruction — server enforces byte-equality between message and instruction when both are required, so different recipient handlers route on the same content).

Sparse-update edge cases pinned

Two tests that pin sparse-update semantics on the new fields against a refactor that conflates "unset" and false-y values:

• passes require_payload_override=false explicitly (clear opt-in) — explicit false must round-trip.
• passes required_payload_keys=[] explicitly (clear list) — empty array must round-trip (server reads it as "no required keys / clear the list").

Tests

7 new (38 → 45 in tests/tools.test.ts, 86/86 total pass). First PR to add HTTP-contract tests for cueapi_create_cue (didn't exist before).

$ npm test
Test Files  5 passed (5)
     Tests  86 passed (86)

$ npm run build
(clean)

Parity manifest

• tool_param_drift.cueapi_get_execution.covered_response_fields now includes payload.
• tool_param_drift."cueapi_create_cue / cueapi_update_cue".covered_request_fields now includes the two new PR #590 fields.
• ported_pr_history: #589 + #590 marked PORTED.

Test plan

• npm test → 86/86 pass
• npm run build → clean
• Manual smoke against staging cueapi:
  • cueapi_create_cue { name: "test", require_payload_override: true, required_payload_keys: ["task", "token"] }
  • cueapi_fire_cue { cue_id: "<created>" } → expect 400 payload_override_required
  • cueapi_fire_cue { cue_id: "<created>", payload_override: { foo: "bar" } } → expect 400 missing_required_payload_keys with missing_keys=["task","token"]
  • cueapi_get_execution { execution_id: "<from-successful-fire>" } → response includes payload field
  • cueapi_update_cue { cue_id, require_payload_override: false } → opt-out succeeds

Parity Impact

Closes 2 entries from parity-manifest.json — see "Parity manifest" section above. Manifest update included in this PR (no follow-up needed).

Companion PRs

• cueapi-cli #26 — MERGED 2026-05-04 17:57 UTC
• cueapi-action feat(http): HTTP transport + OAuth 2.1 + PKCE for remote MCP hosts (0.2.0) #2 — pending
• cueapi-python chore(deps): bump better-sqlite3 from 11.10.0 to 12.9.0 #23 — pending

🤖 Generated with Claude Code