Skip to content

refactor(server): classify orchestration exports - #10275

Merged
juliusmarminge merged 2 commits into
cleanup-server/runtime-internalsfrom
cleanup-server/orchestration-internals
Sep 8, 2026
Merged

juliusmarminge merged 2 commits into
cleanup-server/runtime-internalsfrom
cleanup-server/orchestration-internals

refactor(server): classify thread PR reactor constructor

1c4dfee
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Sep 8, 2026 in 2m 8s

All clear

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.


🔍 Agent activity — 4 tool calls

💭 Inspecting comment placements I need to examine the files to see how comments are placed. The main changes involve removing exports and adjusting documentation comments. I should determine if there's a violation of service conventions related to JSDoc positioning, like whether a comment is added after a decorator. I’ll need to actually view the files to understand the context better before moving forward. This might take a little bit of time, but I’ll figure it out!

1. browse_code — apps/server/src/orchestration/ThreadPullRequestReactor.ts

2. browse_code — apps/server/src/orchestration/ThreadSettlementReactor.ts

3. browse_code — apps/server/src/orchestration/Errors.ts

4. browse_code — apps/server/src/orchestration/runtimeLayer.ts


Agent Credits: 9 credits

Token usage: 6 uncached input · 9,436 cache-read input · 12,718 cache-write input · 522 output
Agent Credits may also include non-token charges from external tools such as web research.