[P3] Superseded waiting offline updates accumulate in Cache Storage #37
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Priority: P3
Type: bug
Source: project review requested 2026-10-26 (second pass)
Location:
scripts/offline/worker.js:51, 71Problem and evidence
Cleanup returns early while an update is waiting. With one tab left open and no update accepted, each deploy installs a full copy that replaces the previous waiting worker, whose cache is never used or deleted: complete caches grow 2, 3, 4, 5, 6 (about 0.6 MB per build).
Suggested correction
When a new copy finishes installing, delete the cache of the waiting build it supersedes (never activated, not a rollback copy, not used by controlled tabs), unless it is the active version.
Acceptance criteria
Retention unit check for superseded waiting copies; browser lifecycle stays at active + waiting copies; existing retention/rollback checks pass; pnpm verify passes.
Scope: maintenance of the educational simulator. Preserve historical R1 acceptance and operational-validation limits.
Fixed on
maintenance/review-2026-10-27in074cc83,78e869d— PR #40.A new install deletes the never-activated waiting copy it replaces; five unaccepted deploys keep 2 complete caches (was 6). Follow-up from independent review: all checks run after the version round trips so an accepted update cannot lose its cache. Retention unit check extended.
Branch verification:
pnpm verify145 tests and release budgets; Chromium/Firefox/WebKit review, replay, compatibility and offline lifecycle checks; CI verify runs #111/#112 pass. Record:docs/MAINTENANCE-2026-10-27.md. Closes on merge of PR #40.