cache-sentinel

Use the --full mode to audit all participant-side layers including Service Worker, IndexedDB, Memory, and MongoDB caches. This cross-verifies cache coherence and backend invalidation logic to catch stale data before it reaches users.

Your Service Worker cache versioning might mismatch the new deployment. Auditing Service Worker cache naming and versioning behavior cross-verifies frontend caches against backend MongoDB collections to ensure old data cannot prevail.

Validate IndexedDB and Memory TTL coherence during live market transitions by checking cache invalidation paths for market open, closed, and partial update states. Use targeted audit modes like --live or --frontend to verify transition behavior.

Yes, you can check only MongoDB cache collections for stale participant data by running a targeted audit with the --mongo mode. This focused approach isolates backend cache collection checks from frontend Service Worker and IndexedDB layers.

The best way to investigate inconsistent PWA cache data reported by users is running a full participant scope audit. It cross-verifies MongoDB cache collections, Service Worker cache behavior, and frontend IndexedDB and Memory TTL coherence to identify divergence.

You should not use a full PWA cache audit when you need to isolate a specific layer during incident investigations. Instead, use focused modes like --sw for Service Worker, --frontend for IndexedDB and Memory, or --live for market transition invalidation paths.