v0.26.7

docs/VHOSTS.md

@@ -206,6 +206,10 @@ it does not reload the vhost, purge cache or intentionally abort active exchange
 request counter is per backend client generation, not per TCP connection. Setting either
 recycle value to `0` disables that trigger independently. `http1_max_buffer_bytes` bounds
 Hyper's adaptive upstream HTTP/1 read buffer per connection; it does not apply to HTTP/2.
+Compatible backend clients are retained across unrelated runtime snapshot rebuilds, so
+generation age, request count and rotation totals remain continuous. A changed backend
+origin, address policy, keepalive settings or connect timeout creates a fresh client
+generation state instead of reusing an incompatible pool.
 Disabling reuse sets the idle pool limit to zero and disables keepalive probes. The idle
 limit is not a separate per-backend active-request cap; global connection/exchange bounds
 still apply. HTTP health probes use separate no-reuse HTTP/1.1 connections.