fix(server): full-access OpenCode threads no longer ask for approvals - #9282

💭 I'm examining the diff to OpenCodeAdapter.ts, checking how it adds an unsafe emit helper via Queue.offerUnsafe and a new auto-reply function using Effect.fn and orElseSucceed, and weighing whether the error-swallowing behavior fits the service conventions I'm checking against. Since the diff is against a merge base and the head is at a later commit, I should pull up the current head version of the file for accurate context.

1. browse_code — In apps/server/src/provider/Layers/OpenCodeAdapter.ts, show the import block at the top of the file, the definition of emit/emitUnsafe, the autoReplyFullAccess function, emitPendingOpenCodeRequest, and the terminal permission.replied handler (around autoRepliedRequestIds). Include line numbers.

2. browse_code — apps/server/src/provider/Layers/OpenCodeAdapter.ts

💭 I'm checking the changed lines for convention violations—the new context field looks fine, but I'm scrutinizing whether using the raw Queue.offerUnsafe inside an Effect service counts as a violation since it bypasses the documented runtime patterns like ManagedRuntime.make and runPromise. I notice autoReplyFullAccess swallows errors silently with Effect.orElseSucceed and no logging, though that's not explicitly called out as a listed convention violation. Tests do cover the behavior change, no new imports or lint suppressions were introduced in the diff, and the Effect.fn usage matches existing patterns, so overall nothing stands out as a clear violation.