feat(opencode): add LSP timeout configuration

[ririnto]

Issue for this PR

Related: #13328

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

This PR adds per-server timeout configuration for configured LSP entries.

It introduces separate timeout settings for the two existing timeout paths:

• timeout.startup for the LSP initialize request
• timeout.diagnostics for the diagnostics wait path

This is related work for #13328, which calls out the lack of a user escape hatch for heavy LSP servers. It also follows the per-server configuration direction proposed in #6997 while keeping the scope limited to configured entries and the two existing timeout paths.

How did you verify your code works?

• Ran bun test test/lsp/client.test.ts test/config/config.test.ts in packages/opencode
• Ran bun typecheck in packages/opencode
• Verified the timeout tests cover both default values and configured overrides

Screenshots / recordings

If this is a UI change, please include a screenshot or recording.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Based on the search results, I found a potentially related PR:

Related PR:

• PR feat(lsp): non-blocking initialization + configurable diagnostics timeout #13332: feat(lsp): non-blocking initialization + configurable diagnostics timeout
  • feat(lsp): non-blocking initialization + configurable diagnostics timeout #13332
  • This PR appears to address similar LSP timeout functionality, specifically for non-blocking initialization and configurable diagnostics timeout. The current PR (21006) implements LSP timeout configuration with timeout.startup for initialization and timeout.diagnostics for diagnostics, which overlaps significantly with PR feat(lsp): non-blocking initialization + configurable diagnostics timeout #13332's goals.

Please verify if PR #13332 is already merged or closed, and whether the current PR (21006) is a reimplementation or enhancement of that work.

[rekram1-node]

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.