Report live view timeouts to parent frame

[robertjamesprior]

tldr

Telemetry only: post live-view connection timeouts and ICE candidate diagnostics from the Neko client to the dashboard parent frame, and let the parent toggle read-only mode without remounting the iframe.

why

• #3736 (GPU live view startup OOM classification) merged into the closed hypeship/live-view-recovery stack, not main. It listens for KERNEL_CONNECTION_TIMEOUT, so the dashboard's classifier has no production trigger until this lands on the image path.
• The 52a22b79 relay-escalation commit that was on this branch's previous head changes global ICE policy (relay-only on retry). That is out of scope for GPU OOM (Steven's review on #3733: retry does not address the confirmed OOM failure path) and is deferred to the generic-recovery rescope.
• The read-only toggle lets the dashboard update read-only without an iframe remount that spikes the first connect to connecting and loses ICE context.

what landed

• images/chromium-headful/client/src/neko/base.ts: on the 15s connect watchdog, post KERNEL_CONNECTION_TIMEOUT to the parent frame with state and candidate summaries (type, protocol, address family).
• images/chromium-headful/client/src/app.vue: accept parent-frame KERNEL_SET_READ_ONLY messages instead of forcing a remount.
• This branch no longer carries the relay-retry commit (52a22b79) or the auto iceTransportPolicy override; those are deferred.
• The neko dependency bump to ICE-candidate-selection logging (16605715) went away as well — not needed for parent-frame telemetry.

out of scope

• Retry escalation and ICE policy changes; they belong in the generic-recovery rescope, not in telemetry.
• A full audit of ICE lifecycles with routing policies, rate limits, and hard state resets.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 8c850ad. Configure here.}

[cursor]

Parent lock loses local lock

Medium Severity

Parent-frame lock calls release and then setLocked(true), but the control/release handler runs remote.reset(), which clears locked. The local lock that is supposed to block input even if hosting is granted again does not persist, so a later control/locked can restore input while the embedder still believes the view is read-only.

 

^{Reviewed by Cursor Bugbot for commit 8c850ad. Configure here.}