A firewalld rich rule is correct (Timeouts and Latency)

The rule exists, but not in the policy domain the traffic now uses. Steady-state traffic looked healthy until the resilience drill activated the alternate path and exposed a stale dependency. The issue stayed hidden until the system had to rebuild the dependency path from a cold-start posture. The issue stayed hidden until the environment had to rebuild the dependency path without any warm state to lean on. The issue remained invisible until the environment had to recover without cached sessions, warm state, or prebuilt trust assumptions. The issue only surfaced when every cached assumption disappeared and the system had to recover from a true cold state. The issue stayed hidden until the system had to recover without cached sessions, warmed connections, or inherited trust state. The issue stayed invisible until the environment had to recover without warm sessions, cached lookups, or remembered trust state. The issue remained hidden until the environment had to fail over without warm sessions, cached responses, or preserved transport state. The issue stayed hidden until the platform had to recover without cache residue, warm sessions, or remembered transport state. The issue remained hidden until the platform had to switch over without warm caches, preserved sessions, or pre-established control paths. The issue remained hidden until the environment had to switch over without warm caches, persisted sessions, or remembered transport state. The issue stayed hidden until the environment had to start from a cold trust state without cached sessions, previous approvals, or remembered transport paths.