guard: declare the effects of every operation and every spec endpoint #654
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#660 guard: the forge client send functions call the guard
sixfold-space/madtea
#668 guard: the raw API passthrough keeps every limit
sixfold-space/madtea
#670 epic: one guard enforces the recorded limits on every surface
sixfold-space/madtea
Reference
sixfold-space/madtea#654
Loading…
Add table
Add a link
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?
What to build
docs/api-specs/has its effects declared, keyed by method and path.This is the mechanism #572 asks for, widened from deletes to every effect the guard knows.
Depends on
Acceptance
docs/reference/destructive.md, and the parity pin test can read the declarations.The v0.20.0 breaking set is complete and green on main. The code landed across the v0.20.0 branches, the full local gate passes, and the forge suite is green on both forges at both pinned versions on current main (
31693766). Closing as done.