Improved Dispatcher Cache Invalidation for AEM Content Fragments

[#1]

Request for Feature Enhancement (RFE) Summary:	Enhance Dispatcher cache invalidation mechanisms to support automatic, granular purging of cached content fragment updates without manual rule configuration.
Use-case:	Organizations using AEM Content Fragments heavily rely on Dispatcher caching for performance. When content fragments are updated or versioned, the cache often does not invalidate automatically, leading to stale content being served until manual cache flushes occur.
Current/Experienced Behavior:	Dispatcher requires explicit cache flush rules or manual cache invalidation after content fragment changes. This is error-prone, inefficient, and can lead to content inconsistencies on live sites.
Improved/Expected Behavior:	Provide built-in intelligent cache invalidation that automatically detects changes in content fragments (including variations, tags, or linked metadata) and triggers selective Dispatcher cache purges. This reduces operational overhead and ensures up-to-date content delivery.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM 6.5.x (including Cloud Service), Dispatcher configurations with typical cache rules, Content Fragments managed via AEM Assets
Customer-name/Organization name:
Screenshot (if applicable):
Code package (if applicable):

[#2]

@SantoshSai Thanks for proposing this idea. This has been reported to the engineering under the internal reference SITES-33584. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.