CacheManager

Corex\Cache\CacheManager · class · Core layer

The one way CoreX clears a cache (spec 078, FR-010/011/013). clear() walks declared entries. It never matches a pattern. That is the design decision the whole spec rests on: a delete ... LIKE 'corex_%' is shorter and would remove every rate-limit counter and every spent-captcha token, because both live in corex_* transients. Walking a declared list means the registry’s classification is consulted for every removal, so no scope — including one added years from now — can reach security state. Reading and writing go through {@see CacheStore}; this adds the operations that need to know what a value is rather than merely where it lives.

Public API

__construct(CacheStore $store, CacheRegistry $registry)

store(): CacheStore

registry(): CacheRegistry

clear(CacheScope $scope, bool $confirmed): CacheOutcome

Clear what this scope covers, and report everything it did not.