Release Notes: Chrome Extension 0.1.80

Version 0.1.80 fixes the background-owned bridge WebSocket handshake introduced in 0.1.79.

What Changed

  • The extension background no longer reports bridge connection success until the WebSocket has actually opened.
  • If the background WebSocket errors, closes before opening, or times out, the extension reports a connection failure instead of leaving the content runtime in a false connected state.
  • Background transport diagnostics now record failed open attempts with the bridge URL, tab id, runtime id, and error message.

Why It Matters

The 0.1.79 HTTPS transport change moved ws://.../extension out of the page context and into the extension background. That was the right transport owner, but the first implementation acknowledged the connection before the socket opened. When the bridge URL was wrong or unreachable, the content runtime could stop using its direct reconnect path while the bridge never received runtime_ready.

Verification

  • Added a regression test where the background WebSocket fails before open; the bridge-connect response now returns ok: false.
  • Ran the bridge/reconnect characterization slice.
  • Ran the full overlay runtime characterization suite.