Expose fail-when postconditions on inline HTTP grants #267
Labels
No labels
burndown-2026-06
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/umbra#267
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Outcome
Allow inline opcore grants used by ward-mcp to reject semantically invalid 2xx responses with a JMESPath fail-when predicate.
Required behavior
Motivating case
Forgejo accepts an unknown numeric issue-label ID with HTTP success and an empty resulting label set. The deploy Forgejo MCP must compare the requested $labels with the returned label IDs and fail loudly instead of accepting the no-op.
Refs coilyco-bridge/deploy#247.