From 5899d4e7d84046fe0c81bdd4c49875a0f4e9db88 Mon Sep 17 00:00:00 2001 From: "openai-code-agent[bot]" <242516109+Codex@users.noreply.github.com> Date: Fri, 13 Feb 2026 00:59:07 +0000 Subject: [PATCH 1/2] Initial plan From 0eda42a8e861d120aaac4280b39a73651675682d Mon Sep 17 00:00:00 2001 From: "openai-code-agent[bot]" <242516109+Codex@users.noreply.github.com> Date: Fri, 13 Feb 2026 01:01:52 +0000 Subject: [PATCH 2/2] docs: note dotnet happy eyeballs considerations --- docs/architecture/ARCHITECTURE.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/architecture/ARCHITECTURE.md b/docs/architecture/ARCHITECTURE.md index 7d522cc7..2e00ea3e 100644 --- a/docs/architecture/ARCHITECTURE.md +++ b/docs/architecture/ARCHITECTURE.md @@ -476,6 +476,11 @@ Client Server - Resume from last checkpoint - Pending operations buffered in offline queue +**IPv4/IPv6 Dialing (Happy Eyeballs):** +- .NET 11 preview adds `ConnectAlgorithm.Parallel` to `Socket.ConnectAsync`, enabling Happy Eyeballs (RFC 8305) for WebSocket/TCP dials ([release notes](https://github.com/dotnet/core/blob/main/release-notes/11.0/preview/preview1/libraries.md#happy-eyeballs-support-in-socketconnectasync)). +- SyncKit does not ship a .NET/WebSocket client today, so there is no immediate code change. +- If a C# client is added later, target .NET 11+ and opt into `ConnectAlgorithm.Parallel` (or equivalent) to avoid IPv6-only stall/regression risks when connecting to the WebSocket server. + --- ## Conflict Resolution