How do you handle Angular service-worker updates without breaking active users?

Deployment keeps adjacent versions compatible long enough for active clients and does not immediately delete chunks referenced by older shells. I test first install, offline restart, a new deployment during a session, deferred reload, failed chunk load, and rollback. Service-worker incidents need a recovery path that can bypass or unregister a bad worker when necessary. Metrics distinguish adoption lag, update failure, offline use, and ordinary API cache misses.