feat(security): close capability policy (#690) - #749
Conversation
…de, UAT Add session-scoped exact-scope approvals, sandbox required→blocked degrade, trusted-evidence guards, and UAT-SECURITY-1..7 coverage so #690 can close.
CodeDecay PR CheckLead catch: No direct high-signal catch found CodeDecay did not find a strong direct regression or weak-test signal in this run. Risk: Medium · Merge 39/100 · Decay 54/100 · Security 0/100 This score is conservative pending stronger direct evidence. Treat structural-only signals as review guidance, not proof of a regression. Full CodeDecay reportCodeDecay ReportOverall risk: Medium
Changed Files
Likely Impacted Areas
Normalized Impact GraphGraph artifact:
Symbol Impact EvidenceGraph artifact:
Language And Parser Coverage
Merge Risk Breakdown
Top contributors:
Dampeners:
Notes:
Decay Risk Breakdown
Top contributors:
Dampeners:
Notes:
Security Risk Breakdown
Security Matcher Coverage
Test Evidence
Changed Path Test Proof
Untrusted Memory Context
High Risk Findings
Medium Risk Findings
Low Risk Findings
Recommended Checks
NotesCodeDecay is deterministic and local-first. This report was generated without telemetry, API keys, LLMs, or model calls. Found by CodeDecay - deterministic, local-first, no telemetry. |
Summary
required→blocked degrade (never silent full access), MCP confirmation scope binding, and trusted-evidence guards against forged agent/tool claims.capabilityPolicy.sandbox: best-effort.Closes #690
Test plan
vitest run packages/execution/test/capability-uat.test.tsvitest run packages/execution/test/capability-policy.test.tsvitest run packages/config/test/capability-policy.test.tstsc -p tsconfig.base.json --noEmitMade with Cursor