Extension host crashes on startup in 1.130 and 1.131; createProxyAuthorizationLookup named export not found in @vscode/proxy-agent (works fine on 1.129)

Does this issue occur when all extensions are disabled?: Yes (reproduces also with `--profile-temp`, so it's neither an extension nor a corrupted profile/settings issue).

Version: 1.131.0
Commit: e4c7e7b1d6d060162f4aa7f8225271b67ce1df75
Date: 2026-07-28T10:51:25Z
Electron: 42.7.0
ElectronBuildId: 14710161
Chromium: 148.0.7778.280
Node.js: 24.18.0
V8: 14.8.178.38-electron.0
OS: Linux x64 5.15.0-157-generic

## Steps to Reproduce
1. Launch VS Code 1.131 (also reproduces on 1.130) with `code --disable-extensions`
2. Extension host starts, then crashes almost immediately
3. VS Code shows "Extension host terminated unexpectedly 3 times within the last 5 minutes" and automatically restarts the extension host, which crashes again in a loop
4. Same result with `code --profile-temp`

## Relevant error from Developer Tools console
Extension host (LocalProcess pid: ) terminated unexpectedly. Code: 1, Signal: unknown
```
SyntaxError: Named export 'createProxyAuthorizationLookup' not found. The requested module '@vscode/proxy-agent' is a CommonJS module, which may not support all module.exports as named exports.CommonJS modules can always be imported via the default export, for example using:
import pkg from '@vscode/proxy-agent';
const { createProxyAuthorizationLookup } = pkg;

at (.../out/vs/workbench/api/node/extensionHostProcess.js:675)
at #asyncInstantiate (node:internal/modules/esm/module_job:327:21)
at async ModuleJob.run (node:internal/modules/esm/module_job:431:5)
at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:643:26)
at async file:///.../out/bootstrap-fork.js:590:1191
Node.js v24.18.0
```
[vscode-console.txt](https://github.com/user-attachments/files/30660864/vscode-console.txt)

This repeats identically on every extension host restart, and the crash loop continues until VS Code gives up.

## Additional notes
- I have no proxy-related environment variables set (`printenv | grep -i PROXY` only shows `UBUNTU_MENUPROXY=1`, which is unrelated), so this doesn't appear to depend on proxy configuration.
- The error is a Node.js ESM/CJS interop failure: `@vscode/proxy-agent` is CommonJS, and Node's static named-export detection (cjs-module-lexer) is failing to recognize `createProxyAuthorizationLookup` as an export when imported via `import { createProxyAuthorizationLookup } from '@vscode/proxy-agent'` in extensionHostProcess.js.
- This coincides with the "agent host" rearchitecture mentioned in the 1.131 release notes as having been rolled out "over the last few releases" —
possibly a related change to extension host process bootstrapping/module loading, though I haven't confirmed a direct link.

[vscode-console.txt](https://github.com/user-attachments/files/30660864/vscode-console.txt)