feat: link pull requests to threads - #8160

💭 I'm checking the diff for Effect service convention violations, looking at the new migration file and confirming it uses proper namespace imports, then verifying the test file's import style looks correct too. The client-runtime pullRequests.ts file just uses an atom family helper, not a service, so that's not a concern. I'm now scanning the other touched files to make sure imports are consolidated properly from "effect".

1. browse_code — apps/server/src/persistence/Layers/ProjectionThreads.ts

2. browse_code — packages/client-runtime/src/state/pullRequests.ts

💭 I want to verify the migration file follows the Effect.gen pattern used elsewhere, so I'll check an existing migration like 041 for consistency. The ProjectionThreadRepositoryShape type is pre-existing and untouched by this PR, so I don't need to worry about it. Now I should check the mobile use-thread-pr.ts client file.

3. browse_code — apps/server/src/persistence/Migrations/04*

💭 Let me check example 040 to compare patterns.

4. browse_code — apps/server/src/persistence/Migrations/040_ProjectionProjectFaviconPath.ts

5. browse_code — apps/server/src/persistence/Migrations/040_ProjectionProjectFaviconPath.test.ts

💭 No violations here, this is React not services. I'm checking the mobile thread PR state file, which creates an atom family at module level using connectionAtomRuntime — I need to see if it's smuggling a shared owned resource into multiple consumers, which would violate the runtime isolation guideline. That runtime is just imported from the connection module, not newly created, so it's fine. The verdict looks like "All clear" for Effect service conventions, though I need to reconcile that with the required JSON output format — I'll set the summary field to reflect a clean result. I'll do one last pass on the reducer and contract files, and glance at the thread PR file for completeness before finalizing.

6. browse_code — apps/mobile/src/state/use-thread-pr.ts

💭 No Effect service convention violations found — everything checks out.