feat(agent-config): AOI-1 drop instance-scope disable for plugins and MCP #742
No reviewers
Labels
No labels
area:agents
area:dashboard
area:database
area:design
area:design-review
area:flows
area:infra
area:meta
area:security
area:sessions
area:webhook
area:workdir
security
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/claude-hooks!742
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "code-lead/730"
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?
Make the type-level capability surface (plugins, MCP servers) a non-negotiable contract: instances cannot disable inherited entries with
enabled=false. Resolver drops instance-scopeenabled=falserows; write path returns 400 with the prescribed message; migration 003 rebuildsplugin_binding/mcp_serverwith CHECK constraints and coalesces AOI-5's prune.Test plan
enabled=falseat instance scope returns 400 with the exact error messagerenderForInstancetest updated to verify the CHECK rejects the legacy shadow attempt while the type baseline survivesbun x turbo run test(3074 tests) greenCloses #730
Three-layer enforcement (write-path → SQL CHECK → resolver filter) is correct and complete. All AC met: resolver ignores
scope=instance AND enabled=falsefor both plugins and MCP;assertAddOnlyInheritanceblocks the write at every entry point (PUT/fork/restore); migration 003 is idempotent and coalesces AOI-5. CI green.