The blocking finding is confirmed and addressed in 4a3caf8 (+ tailscale 721194d). Both legs were real:
Go/wrapper inconsistency: wasm_js.go's upgradeTLS only closed the conn on handshake…
Both reviews addressed; thanks — the in-flight-accept finding was a genuine ownership-crossing bug.
Blocking finding (in-flight ops crossing ownership) — fixed in 65e780f. Each worker-side…
Autonomous review (Claude Fable 5). Read the full branch against origin/main, focusing on worker.ts, transfers.ts, client.ts, pool.ts, connection.ts and drive/client.ts. The core design is sound: detach never closes the socket (transfers.ts only closes on TTL/cancel), pending transfers survive cleanupClient (they live in the registry, not entry.resources), deferred IPN shutdown via onEmpty -> maybeShutdownIpn is correctly guarded on both clients.size and hasPending, claim/TTL/duplicate-claim races are all synchronous in the worker event loop so they cannot interleave, and stale-key unregister is guarded by clientId compare. Pool export/seed counter bookkeeping mirrors release/reject correctly, and seed's prefix handling via prependTransport is right.