[MopigamesYT]

Closes #281

Summary

• The browser client opens and shows its "Connecting to…" sheet, then asks the server to pair, as it did before UI: frosted glass behind dialogs, menus and the drawer; press and arrival animations #247 and Web client: 1loop's remote mode in the browser via wasm (#267) #269 met on dev.
• Dialogs and menus in the browser still get the glass's dark tint, but no blurred copy of the page behind them. The desktop and phone apps keep the frosted glass unchanged.
• If the page ever stops before pairing again, CI's "Check the browser client" log now prints the page's console (usually the panic), not only "the page never asked to pair".

Screenshots

The browser client served by 1loop-server, 5 s after loading (from 1loop-web-smoke):

Before	After

Technical details

• internal/ui/glass.go: frostedBackdrop returns nil when runtime.GOOS == "js", which callers already treat as "canvas not readable" and draw the tint alone. In the browser, CaptureNow → Fyne's WebGL ReadPixels (github.com/fyne-io/gl-js) passes a Go []byte to syscall/js, which panics with ValueOf: invalid value. The first sheet.Show (connectOrigin in web_js.go) killed the page.
• cmd/1loop-web-smoke/main.go: on the pairing timeout, the console lines collected so far are logged before failing.
• Checked locally: make web + 1loop-web-smoke -check passes (pairing, state reads, the event stream, 3 attachments); desktop go build/go vet and wasm go vet ./internal/ui pass.

Assisted-by: Claude Opus 5.5 (claude-opus-5-5) low

🤖 Generated with Claude Code