feat(guard): #654 declare the effects of every operation and spec endpoint #779
No reviewers
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.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!779
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-654-effect-declarations"
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?
Summary
Every first-class operation and every endpoint in the vendored Forgejo and Gitea
specs declares its write effects in one registry (internal/opspec); a Go test
fails the gate on any undeclared operation or endpoint, naming it. Every raw
DELETE endpoint declares unrecoverable-destroy except DELETE /contents (a
recoverable content write); the pure-toggle allowlist is deferred to #774. The
ADR 0029 destructive table, docs/reference/destructive.md, and the parity pin
test now read the single registry - the three hand-maintained maps are deleted.
Refs #654