Skip to content

feat(web): drag sidebar threads between categories - #8001

Open
tarik02 wants to merge 30 commits into
pingdotgg:mainfrom
tarik02:feature/sidebar-dnd-upstream
Open

feat(web): drag sidebar threads between categories#8001
tarik02 wants to merge 30 commits into
pingdotgg:mainfrom
tarik02:feature/sidebar-dnd-upstream

Merge branch 'main' into feature/sidebar-dnd-upstream

f7f6b6b
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Aug 24, 2026 in 8s

Effect Service Conventions: No findings

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 — 2 tool calls

💭 I'm checking the diff in decider.ts, noting the new type imports for CommandId, OrchestrationThread, and ThreadId, which follow the convention of named imports from @t3tools/contracts. I'm also looking at how planThreadCategoryCleanup is typed using Effect.fn. Return, and want to open the actual file to confirm the import structure.

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

💭 This file follows the established import conventions well, using namespace imports from effect subpaths and named imports from allowed packages. I'm checking the other TypeScript files in scope, noting that web hooks sit at the React application boundary and verifying that the sidebar drag-and-drop hook's imports from client-runtime and atom registries are all properly scoped. Since none of these changes create, move, or consume an Effect service, the review checklist doesn't strictly apply here—so I want to double-check via git that the diff file list is complete and no new error classes or services were introduced elsewhere in the PR.

2. git_toolsb1670ac..d4975c7

💭 I don't see any Effect service creation, refactor, or consumption issues here—the decider changes stay within existing conventions, and the schema's use of Effect.succeed is pre-existing. Since everything checks out clean, I need to figure out how to format the "all clear" conclusion given the JSON schema requirement.


Agent Credits: 0 credits
No billable model usage was recorded for this run.