Stop using TypeScript in ./vscode

[jviotti]

The whole thing is 500 lines of code. The amount of boilerplate needed
to setup TypeScript, the build, the extra dependencies, etc seem
overkill for something so simple.

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[cubic-dev-ai]

No issues found across 23 files

[augmentcode]

🤖 Augment PR Summary

Summary: This PR simplifies the VS Code extension by removing the TypeScript toolchain from ./vscode and shipping a plain JavaScript entrypoint.

Changes:

• Replaced the TypeScript extension source (src/extension.ts) with a CommonJS module (vscode/index.js) exporting activate/deactivate.
• Removed VS Code-side TS build/lint infrastructure (tsconfigs, esbuild script, ESLint TS config, and related devDependencies).
• Updated the Makefile to stop running VS Code TS build/lint steps and to package/copy index.js into build/vscode.
• Adjusted VS Code debug configuration to point at JS outputs without a pre-launch build task.
• Moved protocol type declarations under webview/src/protocol and updated webview imports accordingly.
• Relocated the webview TypeScript base config into webview/ and updated webview/tsconfig.json to extend it.

Technical Notes: The VS Code extension now runs directly from vscode/index.js (and build/vscode/index.js for VSIX packaging), reducing build-time dependencies and boilerplate for the extension side.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

updateLintDiagnostics filters out null positions but not undefined; if any CLI error object omits position, errorPositionToRange(error.position) will throw when destructuring. Consider filtering out both null and undefined (or validating the shape) before creating diagnostics.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

This filter only excludes undefined instancePosition, but null (or other non-array values) would still pass and then crash in errorPositionToRange(error.instancePosition) due to destructuring. Consider ensuring instancePosition is a valid 4-tuple before building a vscode.Range.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}