v0.5.2

Three prompt-cache busts fixed on the WebSocket path. All three cost cached tokens silently — nothing failed, requests just stopped hitting the cache.

A token refresh no longer throws away the socket. The connection pool keyed on the bearer token, so a routine OAuth refresh looked like a different account: the next turn opened a cold socket and lost its continuation chain, replaying the conversation at full price. The pool now keys on the ChatGPT account identity, so a refresh keeps its connection. Two accounts still never share a socket.

Sessions that fall back to HTTP keep rotating their turn id. When a session drops from WebSocket to HTTP mid-conversation, the turn id froze at whatever value it last held and stayed there for the rest of the session, breaking the cache on every subsequent turn. Both transports now share one rotation implementation.

A connection limit during prewarm falls back immediately instead of spending a second doomed attempt to learn the same thing.