feat(guard): #653 add the guard package with its three write effects #772
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!772
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-653-guard-package"
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
Adds the guard package (internal/service/guard): three pure, table-testable
write-effect decisions - DefaultBranchWrite, UnrecoverableDestroy,
OutOfScopeContentWrite. Each takes no override, and every refusal names the next
step, never a way around it. The default-branch and destroy effects have no
production caller yet; that wiring is the later #670 children. The
out-of-scope content-write rule moves out of internal/mcp/forgewrite_guard.go
into the package with its behavior unchanged, and the mcp wrapper now delegates.
Per ADR 0046.
Closes #653