fix(server): reuse pr state when settling threads - #9459

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

2. browse_code — apps/server/src/orchestration

💭 The layer exposing FileSystem as a requirement seems fine per conventions, but I want to verify FileSystem is actually provided wherever this layer gets run — that could be a real bug worth flagging. I'm also questioning Effect.orElseSucceed(() => false) here — conventions favor catching statically known tagged failures rather than swallowing the whole error channel, though orElseSucceed does handle it fully so it's not a clear-cut violation. Let me check the runtime layer file to confirm FileSystem is actually supplied.

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

4. browse_code — Where is ThreadSettlementReactor.layer provided/composed, and is a FileSystem layer (BunFileSystem / NodeFileSystem / platform FileSystem) provided in that layer composition? Show the file and code.

💭 I've checked the git service usage, imports, and error handling patterns, and everything follows convention correctly—tests exist for the behavior change, so I can report all clear. Since there's nothing to flag, my final response should just be "All clear" on its own, which I'll pass through the summary field of the complete_check call.