NgRx Store DevTools filter option in v15.0.0: should it also suppress persistence to localStorage?

Goal: decide whether the NgRx Store DevTools filter option introduced in v15.0.0 should also prevent filtered actions from being persisted to the localStorage key used by the DevTools monitor.

Currently the filter only suppresses runtime UI updates and associated console alerts, while actions that match the filter continue to be written to localStorage, which can still accumulate noise in larger applications.

Uncertainty remains about the impact on debugging workflows, storage consumption, and whether existing persisted logs should be migrated or cleared when a filter is applied.

Questions: Should the filter option also block filtered actions from being stored in localStorage? If so, how should the implementation handle already‑persisted entries? What trade‑offs exist between reducing runtime noise and reducing persistence noise?