jcoffey-dev
0ad19802f8
The deploy on 2026-09-08 went out at the origin and did not arrive. Cloudflare went on handing out the previous `sw.js` -- `cf-cache-status: HIT`, with an edge TTL of four hours, longer than the hour we asked for -- because the file is neither a hashed asset nor HTML and so fell into the ordinary `max-age=3600` case. That is not a freshness preference. The service worker is the app's whole update mechanism: a browser holding the old one goes on being served the shell that worker knows and never learns a deploy happened, so the deploy simply does not land. The manifest matters for a second reason -- the two have to agree. A fresh manifest advertising a share target, answered by a worker that has never heard of one, sends the share to the server for a 405. Either being old is survivable; disagreeing is not. `no-cache` rather than `no-store`: both may still keep a copy, they just have to revalidate it, which is a 304 and costs nothing. Neither gets to answer with its own copy without asking. Narrow on purpose -- two files, named, rather than a policy that quietly stops the icons and fonts being cached as well.