Bug: malformed Bedrock host permission breaks Chromium extension load in v1.1.0/v1.1.1

[arnaudassoumani-collab]

Summary

Chromium reports a manifest error due to an invalid host pattern:

https://bedrock-runtime.*.amazonaws.com/*

This breaks clean loading and options/settings behavior in packaged builds that include this pattern.

Affected versions

• chromium-extension-versions/v1.1.0/manifest.json
• chromium-extension-versions/v1.1.1/manifest.json
• chromium-extension/public/manifest.json (source before fix)

Reproduction

1. Load unpacked extension from chromium-extension-versions/v1.1.1.
2. Open chrome://extensions/?errors=<extension_id>.
3. Observe error: URL pattern 'https://bedrock-runtime.*.amazonaws.com/*' is malformed.

Expected

Manifest contains only valid host permission patterns; extension loads with no manifest URL-pattern errors.

Actual

Chromium rejects the wildcard-in-middle hostname pattern.

Proposed fix

• Remove malformed Bedrock pattern from optional_host_permissions.
• If Bedrock support is needed, request explicit region hosts (or route Bedrock through bridge proxy).

Notes

options_ui.open_in_tab remains correctly configured and should keep opening settings in a dedicated tab.