Remote SSH: extension icons/fonts blocked by CORS for vscode-managed-remote-resource after VS Code 1.123.0

Type: Bug

Remote SSH regression: extension-contributed icons/fonts fail to load via vscode-managed-remote-resource

Environment:

• Windows VS Code client over Remote SSH to Linux
• Broken on VS Code 1.123.0 and current Insiders
• Works on VS Code 1.122.1
• Remote - SSH latest; rolling back Remote - SSH alone did not help
• Local Windows projects are fine
• Built-in VS Code Source Control icons are fine
• Extension-contributed remote icons/fonts render as square boxes

Console errors:
Access to image at vscode-managed-remote-resource://.../openai.chatgpt.../blossom-white.svg blocked by CORS
Access to font at vscode-managed-remote-resource://.../eamodio.gitlens.../dist/glicons.woff2 blocked by CORS

Expected:
Remote extension resources loaded through vscode-managed-remote-resource should be accepted like vscode-remote-resource.

Actual:
CORS allowed-protocol list does not include vscode-managed-remote-resource, so extension icons/fonts fail.

Extension version: 0.124.0
VS Code version: Code 1.122.1 (8761a5560cfd65fdd19ce7e2bd18dab5c0a4d84e, 2026-05-29T09:25:37+02:00)
OS version: Windows_NT x64 10
Modes:
Remote OS version: Linux x64

Clarification: I filed this from 1.122.1 after rolling back. The bug reproduces on 1.123.0 and current Insiders, and does not reproduce on 1.122.1.

Start by tracing the CORS allowed-protocol handling for vscode-managed-remote-resource and compare it with the existing vscode-remote-resource path. Reproduce on VS Code 1.123.0 or Insiders with a Remote SSH window; done means extension-contributed SVG icons and fonts load without CORS errors while built-in resources remain unaffected.