Predictive image cache entries persist after config.image_cache_predict is disabled

Ren'Py provides an image cache for decoded textures, influenced by config.image_cache_size and config.image_cache_predict. The design question concerns the cache lifecycle when predictive caching is toggled at runtime.

The configuration change from predictive enabled to disabled is documented, but the expected invalidation semantics for already predicted entries are not clearly specified. Behavior may differ between Ren'Py versions before 8.0 and later versions due to internal cache management changes, and current verification is needed.

What is the intended invalidation behavior for predictive entries when config.image_cache_predict changes from True to False? Is the retention of those entries consistent across Ren'Py 7.x and 8.x? How should developers reason about cache size and memory usage across a configuration transition?