Static asset cache busted but CSS still stale on CDN

Scenario

A theme update deployed successfully, but some visitors still receive old CSS from the CDN or edge cache.

Recommended Resolution Path

1. Check cache-control headers, file naming, and whether the CDN honors origin revalidation.
2. Purge the affected asset path and confirm a new edge fetch occurs.
3. Verify the HTML references the updated asset URL rather than the previous one.
4. Use cache-busting consistently so design fixes appear when intended.

Technician Notes

Document what changed, what confirmed the fix, and whether the issue points to a broader standards gap worth addressing for the client.