forge-cachelisted

# forge-cache: Caching ## Purpose First decide whether caching is justified, then audit keys, invalidation, consistency, privacy, and failure behavior. Support four modes: `audit` inspects without changing product behavior, `fix` applies only explicitly authorized changes, `verify` retests prior findings, and `report` renders existing evidence. If no mode is supplied, use `audit`. ## Trigger conditions Use this module when a request names `forge-cache`, asks about caching, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Detected caches, CDNs, memoization, or a measured proposal to add caching ## When it does not apply - No cache and no measured latency or load need Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - cache clients and configuration - query and request flows - performance evidence Prefer `.forge/project-profile.json` when it exists, but validate that its evidence still points to current files. Read `../fullstack-forge/references/PROTOCOL.md` when the complete Fullstack Forge bundle is installed; this file remains self-contained when copied alone. ## Inspection procedure 1. Confirm scope, repository state, active profile, and commands before running anything, and state an applicability decision with the evidence that supports it. 2. First establish necessity: find the measured bottlene