Cursor Keep Alive

A cursor keep-alive pattern lets a client poll for incremental results from a long-running server operation (for example, streaming a RAG query) without holding an open WebSocket. The server stores partial state keyed by an opaque cursor ID; each request advances or resumes delivery. This works through load balancers and WAFs that block WebSockets, at the cost of extra storage and polling latency.