Repository navigation
fix(contracts): include tool.denied in runtime event types - #9770
Effect Service Conventions: no issues found
All clear
Details
Note
Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.
Only one in-scope file changed: packages/contracts/src/providerRuntime.ts, which adds the "tool.denied" literal to the existing ProviderRuntimeEventType schema union. No service definitions, imports, error classes, or runtime boundaries were touched, so no Effect service conventions apply to the changed lines. The test file packages/contracts/src/providerRuntime.test.ts is excluded by this check's scope patterns.
🔍 Agent activity — 1 tool call
💭 This diff is small, adding "tool.denied" to a Schema.Literals list plus a test. I want to check the providerRuntime.ts file for context since that's the in-scope file, with tests excluded.
1. browse_code — packages/contracts/src/providerRuntime.ts
💭 This is just a schema literal addition, nothing violating Effect service conventions. No findings here, so I can report all clear.
Agent Credits: 13 credits
Token usage: 4 uncached input · 13,107 cache-read input · 15,260 cache-write input · 581 output
Agent Credits may also include non-token charges from external tools such as web research.