Development Update — August 31

A hardening day for the browser visor: a page-freeze fix, an end to two CPU-pegging loops, and a local proxy-status page that answers even before the mesh does. A pair of allocation cuts round it out.

Skywire: The Browser Visor Behaves

4391 stops the standalone page stranding the visor on the page’s main thread, where any long computation froze the UI with it. 4393 ends the in-tab proxy pegging a core against zombie exits and makes the CLI-RPC bridge report honest liveness, and 4394 memoizes the local-route search, widens the proxy dial margin, and recovers a wedged shared-worker boot instead of leaving the tab stuck. 4396 gives the browser visor a local status.skysocks proxy-status page that is never gated by the interstitial — status must be readable precisely when routes are not up yet — and 4397 prefers proxy exits that are already direct transport peers, cutting the time to the first proxied page load.

Skywire: Two Allocation Cuts

4398 memoizes secp256k1 public-key validation, flattening the parse burst when a wasm visor ingests the network’s transport set, and 4392 cuts transient allocations in the transport discovery’s metrics build.