cache-sentinel

What problem does it solve?

It prevents the participant PWA from serving stale or inconsistent data by proactively detecting cache divergence across Service Worker, IndexedDB, Memory, and MongoDB.

Core Features & Use Cases

• Proactive stale detection for the participant app: checks cache coherence across all participant-side layers, ensuring old data cannot prevail over the system state.
• Targeted audits by scope and timing: use focused modes like MongoDB-only, Service Worker-only, frontend (IndexedDB+Memory), or live-experience transitions.
• Live and post-deploy verification: validates TTL behavior during market closed/open, partial updates, and consolidation-driven invalidations.
• Baseline issue verification: re-checks known critical findings (e.g., SW cache version mismatch) to confirm they were fixed.

Quick Start

Run cache-sentinel in full participant scope immediately after a deploy by issuing the command /cache-sentinel --full.