pastilhasandClaude Opus 5
66a41d0813
Follow-up to bc13450, found by actually driving a browser instead of reasoning about one. The
deferred close keeps a remount's socket alive mid-handshake, but `connect` only treated OPEN as
"already ours" — so the re-run built a second socket, overwrote socketRef, and left the first open
forever with its `open` handler bailing on the mismatch. CONNECTING now counts too.
What the browser actually says, headless Chrome against this server, fresh load of /chat/new:
#1 NEW wss://…/api/chat/ws?token=…
#2 NEW wss://…/api/chat/ws?token=…
#1 OPEN
#2 OPEN (neither ever closes, 12s)
header: green dot, no "Disconnected"
So the served code CONNECTS on a fresh load and the Disconnected report could not be reproduced
here — which points the remaining report at the client's cached bundle rather than at this code. The
chunk hash moved e3jsfax5 -> 81jec45w across these edits, so the rebuild is reaching the wire.
Two sockets per load survive this fix and are NOT what it addresses: they come from two separate
`useChat` instances mounting on that route, each with its own refs, so no per-instance guard can see
the other. Left alone deliberately — both connect, and one conversation opening two agent sockets
wants understanding before a fix.
Also retired here: my claim that StrictMode's double-invoke was the trigger. The served bundle has no
dev-only React internals at all (`doubleInvokeEffectsOnFiber`, `runWithFiberInDEV`,
`commitPassiveUnmountEffectsInsideOfDeletedTree`: zero hits), because pm2 runs `bun start` with
NODE_ENV=production.
Typecheck clean. Repro harness is in the session scratchpad, not committed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>