When the server encounters a rollback affecting any authoritative collection, it currently clears the entire in-memory cache (DSS and CSS) rather than just the affected namespace, forcing a full reload from disk.

This is a regression from 8.0 behavior, where a rollback could be traced to a specific namespace (one collection per namespace), allowing targeted cache invalidation. With the move to a single collection holding metadata for all namespaces, we can no longer identify which namespace triggered the rollback, so the whole cache is dropped as a fallback.