Sulu cache invalidation ambiguity for custom content types

Sulu's default caching layer relies on Symfony's cache component to manage content repository responses. When custom content types are introduced through the REST API, the framework does not publish explicit invalidation rules, requiring manual configuration to prevent stale data. This gap affects repeatable development environments where team members must independently reconcile cache behavior across versioned and multilingual content sets. The experimental Symfony 6.4 and PHP 8.3 support noted in the Sulu release matrix may further influence cache invalidation behavior for new projects. The uncertainty centers on whether Sulu provides extension points or event listeners that reliably trigger cache clearing for custom repository operations, and how those interact with the node-based hierarchy and language fallback mechanisms. What mechanisms does Sulu offer for purging cached content when custom content type schemas change? Are there documented event listeners or kernel hooks that guarantee cache invalidation for REST-driven updates? How do versioned content and multilingual metadata factor into the default cache invalidation strategy?