Scope git checkout effects and update Effect/Node dependency set by juliusmarminge · Pull Request #148 · pingdotgg/t3code

1 issue identified (6 code objects reviewed).

• Merge Base: 5e78386
• Head: 8105951

✅	File Path	Comments Posted
➖	`package.json`
➖	`apps/server/package.json`
➖	`apps/desktop/package.json`
✅	`apps/server/src/wsServer.ts`	0
❌	`apps/server/src/provider/Layers/CodexAdapter.ts`	1
✅	`apps/server/src/git/Services/GitCore.ts`	0
✅	`apps/server/src/orchestration/Layers/ProviderRuntimeIngestion.ts`	0
✅	`apps/server/src/git/Layers/GitCore.ts`	0
➖	`bun.lock`

apps/server/src/git/Layers/GitCore.ts

line 1164: The checkoutBranch method spawns a background task refreshCheckedOutBranchUpstream using Effect.forkScoped. This attaches the background fiber's lifecycle to the Scope provided by the caller. When checkoutBranch returns, if the caller-provided Scope is closed (which is the standard behavior when using Effect.scoped to execute an operation), the background fiber will be immediately interrupted before it can complete. This causes the upstream reference refresh to silently fail, leaving the repository state potentially stale, defeating the stated purpose of keeping the checkout responsive. [ Out of scope ]