Reconnect-delay hint (milliseconds) for the standalone server->client SSE
stream on the 2025-11-25 revision. When non-zero, the GET stream emits a
standard SSE retry: event right after opening, so that if the server
later closes the connection without terminating the stream (e.g. to avoid
holding a long-lived socket), the client already knows how long to wait
before reconnecting (basic/transports §Sending Messages item 6 /
§Listening for Messages item 4: "it SHOULD send an SSE event with a
standard retry field before closing the connection. The client MUST
respect the retry field"). This is a 2025-11-25-only SHOULD: it is built
on the connection/stream split and Last-Event-ID reconnect that only that
revision defines, so it never alters 2025-06-18 / 2025-03-26 / 2024-11-05
or draft wire output. When zero (the default) no retry: hint is sent.
Reconnect-delay hint (milliseconds) for the standalone server->client SSE stream on the 2025-11-25 revision. When non-zero, the GET stream emits a standard SSE retry: event right after opening, so that if the server later closes the connection without terminating the stream (e.g. to avoid holding a long-lived socket), the client already knows how long to wait before reconnecting (basic/transports §Sending Messages item 6 / §Listening for Messages item 4: "it SHOULD send an SSE event with a standard retry field before closing the connection. The client MUST respect the retry field"). This is a 2025-11-25-only SHOULD: it is built on the connection/stream split and Last-Event-ID reconnect that only that revision defines, so it never alters 2025-06-18 / 2025-03-26 / 2024-11-05 or draft wire output. When zero (the default) no retry: hint is sent.