fix(opencode): resolve LSP for nested TypeScript sub-projects

[joao-jlcm]

Issue for this PR

Closes #47174

Related to #40413, #35396, #18694 — the same change set addresses all three (the Typescript.root walk covers #18694, the tsserver.js resolution covers #35396, and the $/progress wait covers #40413). Maintainers can decide which to close as superseded when this lands.

Type of change

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

What does this PR do?

The lsp tool returns empty results for .ts files in nested TypeScript sub-projects (each with its own tsconfig.json under the working directory), and for some sub-projects it returns "No LSP server available for this file type." outright.

Three defects in the LSP runtime compound to produce both symptoms.

Typescript.root in packages/opencode/src/lsp/server.ts walks up looking only for lockfiles, never for tsconfig.json. In a layout like the one in the issue (no lockfile at the workspace root), every .ts file resolves to ctx.directory and all sub-projects share one tsserver client that never learns about the sub-project's tsconfig.json.

Typescript.spawn resolves typescript/lib/tsserver.js from ctx.directory via createRequire(path.join(dir, "package.json")). When the opencode working directory has no package.json, the call returns undefined and the key is marked broken, which is what produces the "No LSP server available" error.

packages/opencode/src/lsp/client.ts has a window/workDoneProgress/create handler that returns null (silently dropping the progress token) and no $/progress listener. typescript-language-server relays tsserver's projectLoadingStart / projectLoadingFinish as standard $/progress notifications, so the first request races tsserver's project load and gets [].

Changes:

• packages/opencode/src/lsp/server.ts: include "tsconfig.json" in Typescript.root's include patterns (nearest wins, fully backward compatible) and resolve tsserver.js from the sub-project root first with a fallback to ctx.directory.
• packages/opencode/src/lsp/client.ts: return the token from window/workDoneProgress/create, listen for $/progress, expose an awaitProgress(timeoutMs) helper, and call it (5 s budget) after the cold didOpen path for the typescript server.

How did you verify your code works?

• bun typecheck in packages/opencode is clean.
• bun test test/lsp/typescript-root.test.ts — 7 new tests covering nested tsconfig, sibling sub-projects resolving to distinct roots, tsconfig-over-lockfile priority, lockfile-only fallback, no-markers fallback, deno exclusion, and distant-lockfile.
• bun test test/lsp/ test/tool/ test/config/ — 636 pass, 3 skip, 0 fail. Existing jdtls-root.test.ts, lsp/client.test.ts, lsp.test.ts (tool), and config/lsp.test.ts are all unaffected.

End-to-end repro against the layout in #47174 (one scratch workspace with frontend/, backend/, website/, sdk-ts/ each containing a tsconfig.json):

• documentSymbol, hover, goToDefinition on frontend/src/lib/services/query.service.ts returns non-empty results.
• Same operations on sdk-ts/src/client.ts no longer throw "No LSP server available for this file type.".
• bun run packages/opencode/src/cli/cmd/debug/lsp.ts status reports two connected typescript clients rooted at each sub-project (different cache keys per tsconfig.json).

Screenshots / recordings

Not applicable — non-UI change.

Checklist

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

[github-actions]

Thanks for updating your PR! It now meets our contributing guidelines. 👍