Validate subscription recovery under cache pressure

Outcome

Reconnection and cache eviction must not remove protected accounts, overwrite local execution, or lose the tracking needed to finish undelegation.

The current LRU scenarios measure eviction and refetch behavior without combining it with these account lifecycle states.

Scope

Prepare three groups: read-only accounts updated on base, delegated accounts modified only on ER, and accounts waiting for undelegation completion.

Access enough additional read-only accounts to force cache churn. Repeatedly disconnect base WebSockets, create new subscriptions while resubscription is running, and release delayed older observations after newer state has been seen through another channel.

Continue transactions using already-materialized delegated accounts throughout the sequence.

Acceptance criteria

• Delegated and undelegating accounts remain present and cannot be replaced by stale remote state.
• Read-only accounts eventually reflect the latest confirmed base values.
• Undelegation completion is still discovered during or after reconnect.
• Warmed traffic and new subscriptions recover within the scenario deadline rather than remaining permanently stalled.