fix(lsp): increase initialize timeout for JDTLS and KotlinLS

Add an optional initializeTimeout override to the LSP server Handle and
honour it in the client initialize call, defaulting to 180s for JDTLS and
KotlinLS which routinely exceed the 45s default on first project load.

Ported from anomalyco#25649 (adapted for the Effect layer).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: randomvariable

packages/opencode/src/lsp/client.ts

@@ -249,7 +249,7 @@ export async function create(input: {
         },
       },
     }),
-    INITIALIZE_TIMEOUT_MS,
+    input.server.initializeTimeout ?? INITIALIZE_TIMEOUT_MS,
   ).catch((err) => {
     throw new InitializeError({ serverID: input.serverID, cause: err })
   })

packages/opencode/src/lsp/server.ts

@@ -25,6 +25,8 @@ const output = (cmd: string[], opts: Process.RunOptions = {}) => Process.text(cm
 export interface Handle {
   process: ChildProcessWithoutNullStreams
   initialization?: Record<string, any>
+  /** Override the default 45 s initialize-request timeout (ms). */
+  initializeTimeout?: number
 }
 
 type RootFunction = (file: string, ctx: InstanceContext) => Promise<string | undefined>
@@ -1266,6 +1268,7 @@ export const JDTLS: Info = {
           cwd: root,
         },
       ),
+      initializeTimeout: 180_000,
     }
   },
 }
@@ -1354,6 +1357,7 @@ export const KotlinLS: Info = {
       process: spawn(launcherScript, ["--stdio"], {
         cwd: root,
       }),
+      initializeTimeout: 180_000,
     }
   },
 }