Lumen file cache TTL persistence beyond configured expiration

Lumen's default file cache driver is documented to expire entries after a configured time-to-live, yet entries often remain accessible past their TTL if the cache store is not explicitly cleared. This discrepancy between documented expiration and runtime behavior raises questions about data freshness guarantees.

The file driver does not support cache tagging, restricting granular invalidation to key-level operations only. Moreover, cache invalidation behavior diverges between Lumen 9.x (based on Laravel 9) and Lumen 10.x (aligned with Laravel 10), meaning TTL enforcement and available methods may shift across minor version upgrades. In production settings, file-level locking under concurrent requests can further entrench stale reads, as the driver may retain a serialized value beyond its intended lifespan.

Does Lumen guarantee TTL enforcement for file cache entries across versions 9 and 10.x? What viable mechanisms exist to invalidate a specific cached key when underlying data changes without clearing the entire store? Is there a version-aware approach that satisfies TTL compliance while mitigating file-locking risks in concurrent environments?