class CatalogueCache implements ConfigCacheInterface
Decides whether a compiled catalogue still reflects the translations this instance has been given.
Symfony names a catalogue after its fallback locales alone, and outside debug mode considers it fresh if the file simply exists — so once written, nothing detects that the translations behind it changed. Enabling an extension on one instance leaves every other instance serving a catalogue that predates it, with no mtime, TTL or revision that would ever say otherwise. So each revision gets its own catalogue, named after it. The revision is derived from what the instance can see for itself, so an instance that was never told anything still looks for a catalogue that does not exist yet, and builds it. Because the name carries the revision, a catalogue cannot be paired with a revision it was not built for, instances on different revisions (old and new servers during a deploy) each keep their own, and no opcache anywhere holds an older compile under that name. Catalogues of earlier revisions stay until the cache is cleared, which every change of revision in core comes with. Freshness is decided per locale, because Symfony compiles catalogues lazily per locale: a request for `de` never touches `en`. A locale nobody asks for therefore costs nothing, and rebuilds the moment it is first requested — where previously it would have stayed stale indefinitely. Outside debug mode, registered resources are never asked whether they are fresh. Doing so would run third-party {\Symfony\Component\Config\Resource\SelfCheckingResourceInterface} implementations that have never executed outside debug mode, some of which resolve services and query the database on every request. In debug mode they are asked, as Symfony's own cache did, so an edited translation file shows on the next request.