feat(action): forward --verify opt-in flag for fire (cueapi-cli #55 parity)#17
Merged
Merged
Conversation
…arity)
cueapi-cli #55 added a --verify opt-in flag to the `fire` command for
Phase 2 body-verify (Mike directive 2026-05-11). The Action's fire step
should forward it so GitHub Actions callers can opt into body-verify
on cues fire from their workflows.
## Why opt-in for fire (vs default-on for messages)
Substrate /v1/cues/{id}/fire echoes a pydantic-after-parse body that
may include server-side default-population, causing spurious diff vs
the CLI's canonical-JSON serialization. So fire's verify is opt-in;
messages' verify is default-on (different endpoint, different echo
semantics post-#798 spec-lock).
## Change
- Adds a new `verify` action input (default empty/false).
- Sets `VERIFY: ${{ inputs.verify }}` env in runs.steps.
- Wires `[ "$VERIFY" = "true" ] && cmd+=(--verify)` into the fire case.
## Naming clarity
The `verify` input is intentionally NOT the same as `no-verify`:
- `no-verify`: messages-send / message-to (default-on opt-out — verify-on by default)
- `verify`: fire (default-off opt-in — verify-off by default)
Both inputs are documented with the divergence noted explicitly.
## Out of scope
- No test framework in cueapi-action (action.yml + shell). YAML validates;
the runtime path was inherited from the cli #55 changes which have
219/219 tests passing including `test_fire_verify_*`.
Companion PRs:
- cueapi-cli #55 (--verify flag)
- cueapi-python #41 (auto_verify kwarg)
- cueapi-mcp #36 (auto_verify schema field on cueapi_fire_cue)
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
cueapi-cli #55 added a
--verifyopt-in flag to thefirecommand for Phase 2 body-verify. This PR forwards the flag from the Action to the CLI so GitHub Actions workflows can opt into body-verify on cues fire.Why opt-in for fire (vs default-on for messages)
Substrate
/v1/cues/{id}/fireechoes a pydantic-after-parse body that may include server-side default-population, causing spurious diff vs the CLI's canonical-JSON serialization. So fire's verify is opt-in; messages' verify is default-on (different endpoint, different echo semantics post-#798 spec-lock).Change
verifyaction input (default empty/false)VERIFYenv var to the fire case inruns.steps[ "$VERIFY" = "true" ] && cmd+=(--verify)into the fire shell caseNaming clarity
The
verifyinput is intentionally NOT the same asno-verify:no-verifymessages-send/message-toverifyfireBoth inputs are documented with the divergence noted explicitly.
Companion PRs in the body-verify Phase 2 stack
--verifyopt-in flagauto_verifykwargauto_verifyschema field🤖 Generated with Claude Code