You can now skip the handshake and still call a tool and your retry after a timeout can place two requests. We ran the retry on one laptop. The tool slept 2.5 seconds on purpose. > Wait 2.5 seconds > Abort around 400 ms > Log already at 1 > New id, second write Same sku. Same machine. A new request id is now a new call. Google said the old pin returned 400 Session Not Found on the wrong pod. GitHub already dropped Redis session reads and writes. Claude-only apps can often wait. Server authors cannot treat a hang-up as a rollback. What keeps a retry at one write? Where does a cart live with no session id? Do you still advertise the old revision?