Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

task(desktop): note which phone copies the parity test still holds

tonycf2cc494fcdd
diff --git a/desktop/CLAUDE.md b/desktop/CLAUDE.md
index f680988b5..19c80a1dd 100644
--- a/desktop/CLAUDE.md
+++ b/desktop/CLAUDE.md
@@ -152,9 +152,16 @@ Each relay connection also negotiates a WebRTC data channel to the machine
(`web/p2p/`, the phone's `../mobile/lib/p2p` on the browser's own
`RTCPeerConnection` — no `flutter_webrtc`, so native builds gain no plugin);
terminal frames take it when it is up and fall back to the relay. Those files,
-the transport interface and the E2EE session are copies of the phone's (mobile
-stays a standalone package); `test/p2p/mobile_parity_test.dart` fails until a
-change is carried to both. The browser's E2EE is pure Dart on the UI thread,
+the transport interface and the E2EE session began as copies of the phone's
+(mobile stays a standalone package). `test/p2p/mobile_parity_test.dart` still
+holds two of them to the phone's — the link (`web/p2p/terminal_p2p_link.dart`)
+and the transport interface (`ws/terminal_transport_plugin.dart`) — and fails
+until a change is carried to both. The P2P plugin and policy, the relay codec
+and the E2EE session differ on purpose since 2026-10-14: the phone starts its
+channel on the first terminal with no open wait, redials a dropped one within
+seconds, and works the hello, the welcome and large frames on a background
+isolate; the browser keeps its own copies, so a fix to one of them is carried
+across by hand. The browser's E2EE is pure Dart on the UI thread,
and that is fine: sealing plus opening a 4 KiB frame measured 316 µs under
dart2js `-O4`, 282 µs on the Dart VM and 479 µs as `-O4` WASM (Node 24,
2026-10-06) — `flutter test --platform chrome` compiles unoptimized and reads