caching Shipped
What this lens looks for
Server controls cache policy via headers; immutable versioned assets use public, max-age=31536000, immutable; dynamic API responses use private, max-age=N; sensitive/mutation responses use no-store; ETags for conditional requests; post-mutation cache invalidation
What its verifier checks
Immutable assets have long-lived Cache-Control: immutable; sensitive responses have Cache-Control: no-store; ETag headers present on cacheable resources; mutations invalidate related cache entries