Bump vscode languageserver to 10

[JustinGrote]

The LSP client now supports v3.18, we should bump to it and verify no breaking changes affect us.

[github-actions]

Dependency upgrade: bump vscode-languageclient from v9 → v10 to gain LSP protocol v3.18 support.

For maintainers

Current state
package.json pins:

• vscode-languageclient: ^9.0.1
• vscode-languageserver-protocol: ^3.17.5

The target is vscode-languageclient@^10.x / vscode-languageserver-protocol@^3.18.x. The v3.18.0 / client-10.0 changelog should be reviewed for breaking API changes before merging.

Reproducibility
N/A — this is an enhancement/task, not a bug report.

Copilot-fix suitability: Yes
Well-scoped, localized change with a clear expected outcome:

1. Bump vscode-languageclient to ^10.x and vscode-languageserver-protocol to ^3.18.x in package.json.
2. Run npm install and npm run compile to surface any TypeScript breaking changes.
3. Fix any API mismatches (primarily in src/session.ts and wherever LanguageClientOptions / request/notification types are used).
4. Run npm run lint and npm run format.
5. Verify the extension still starts correctly against PSES.

Low design risk; the changelog provides a concrete list of what changed.

Likely area

• package.json — version bump
• src/session.ts — primary consumer of vscode-languageclient APIs
• src/features/ — any feature that registers custom LSP request/notification types

Generated by Agentic Issue Triage for issue #5533 · 61.1 AIC · ⌖ 12.7 AIC · ⊞ 23.4K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@2f03fdaafb8c1ae62dfde7e0be762a822a201aeb