985db37cad
Constructor backgroundColor with alpha is silently treated as opaque on a non-transparent window (Electron only documents constructor alpha with `transparent: true`), so windows created while glass was persisted were born with an opaque backing and the vibrancy material never showed — exactly the state a user lands in after toggling glass on and relaunching, or when the renderer re-reports the persisted state at boot (the IPC handler correctly dedupes it, so no runtime swap ever fired). Measured on macOS 26 / Electron 40 (side-by-side spike windows, pixel luminance): ctor '#00000000' = flat opaque (lum 38, same as no glass); omitting backgroundColor entirely = vibrancy visible (lum 57). Runtime setBackgroundColor swaps are also LOST while a fresh process's compositor is settling — swaps at 1s/3s/6s after creation never landed, including from 'ready-to-show' and 'did-finish-load'; a 10s swap stuck. So cold launches must be right at creation: windowBackingOptions() spreads either {} (glass) or the themed anti-flash backing (everything else) into the three chat-window constructors. The runtime swap path stays for live Settings toggles, where the window is long settled.