- Reinitialize_returns_both_backends_to_Healthy — drives
ReinitializeAsync on each backend, asserts DriverState.Healthy
afterwards, then re-reads a 3-tag sample to confirm the runtime
surface is back. Recovery latency isn't pinned tightly (legacy = pipe
+ MxAccess COM client, mxgw = re-Register gw session — different
cadences are expected).
- Health_state_diverges_only_when_one_backend_is_in_recovery — soft
pin that both backends sit in Healthy or Degraded after init.
A tighter fault-injection scenario (toxiproxy-style) is the 5.7
follow-up — landed when the parity rig grows that capability.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
80a0ca2651