Forced-open circuit breaker state after runtime max_connections adjustment

The investigation addresses whether Envoy's circuit breaker can transition from forced-open state when the listener's connection limit is adjusted at runtime, without requiring a full configuration reload. This behavior impacts traffic routing when downstream retry mechanisms are active, especially in deployments that combine listener-level and per-route limits.

Version-specific implementations may evaluate the threshold differently, and the interaction between retry_policy settings and the forced-open condition is not fully documented. Additionally, runtime updates to connection limits might be subject to caching or admin-triggered reloads, creating uncertainty about when the state reflects the new value.

Does the circuit breaker re-evaluate the updated limit on each new connection attempt, or does it maintain the prior state until an admin reload? How does the downstream retry_policy influence the threshold during concurrent connection teardowns? What is the minimal change required to reset the circuit breaker state without disrupting established connections?