Warning: Could not restore navigation state from cache; falling back to initial state – handling stale cache entries

Developers using React Navigation’s state persistence often encounter the warning 'Warning: Could not restore navigation state from cache; falling back to initial state.' when a screen removed from the navigator configuration remains present in the persisted state. The goal is to allow applications to detect and handle these stale cache entries without forcing a full reset to the initial screen, thereby preserving deep‑linking integrity and reducing unexpected navigation flows.

Currently the library does not provide a mechanism to intercept stale cache detection, requiring manual clearing of AsyncStorage or similar stores after each navigator change. An unresolved design decision is whether to expose an optional callback (e.g., onStaleCache) that developers can implement to log, transform, or discard outdated route names before state restoration. Introducing such a callback raises questions about its signature, timing relative to the linking process, and compatibility with existing persistence adapters.

Should React Navigation accept an onStaleCache option in the linking configuration, and if so, what parameters (e.g., array of stale route names, current persisted state) should it receive? How would this callback be invoked relative to the existing state restoration logic, and what guarantees would it provide about not interfering with normal navigation flow?