Extension Activation Failure: Product ID Mismatch in VSCodium

VSCodium is built from the MIT-licensed VS Code source but strips proprietary branding and telemetry. This process modifies the internal product identifier used by the application to identify itself to extensions.

Certain extensions are hard-coded to target the vscode product ID. When these extensions are installed via the Open VSX Registry, they may fail to activate or exhibit degraded functionality because the VSCodium environment does not match the expected identifier required by the extension's activation events.

• How does VSCodium handle extensions that strictly validate the vscode product ID during the activation phase?
• Is there a documented mechanism to alias the product ID for compatibility with these specific extensions?