5 Commits

Include renames

Author	SHA1	Message	Date
Lucas WintherandClaude Opus 5.5	ab3173adf0	fix(refresh): don't call a stored copy "nothing newer", and point an entry at its feature ... When the network failed behind the service worker, it answered from its own store. Check for new data then said nothing newer was published when the server was never reached. The worker now marks that copy, and a fresh check treats it as unreachable; ordinary loads still use it offline. The built-in tasks entry linked to a follow-up fix instead of the feature, and the changelog spec's details now match what shipped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 14:31:04 +02:00
Lucas WintherandClaude Opus 5	a4ab5aa36c	feat(sw): offer a reload when a newer version is ready ... The shell is served cache-first, which is what makes the app work on a train and also what makes a deploy invisible: a reader with the tab open — the reader this app is built for — keeps running the bundle they first loaded, so a new game or a corrected date reaches their device and sits there with nothing saying why the page looks unchanged. An old app shown as current is the same failure as old events shown as current. So the worker now installs quietly and waits instead of calling skipWaiting(), the page notices it waiting and says so, and the reader's tap sends the skip-waiting message and reloads on controllerchange. The app never reloads itself: someone may be mid-way through typing in one of their own events, and the notice says what a reload costs (their place on the page) and what it does not (marks and notes live in localStorage). Detection is derived rather than remembered. build:static grew into a script that stamps sw.js with a hash of the built shell, because the browser only offers a worker whose bytes differ, and the predecessor — a hand-bumped CACHE_VERSION — had already been forgotten once. The feed is deliberately not part of that hash: it changes twice a day, needs no reload, and announcing it would teach readers to dismiss the notice unread. The cache name stays put for the same reason a per-build one would be wrong — it holds the feed an offline reader is reading. A first install is not an update and stays silent. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-17 18:55:08 +02:00
Lucas WintherandClaude Opus 5	7130a94b21	fix(sw): bump the cache version for the F13 bundle ... The shell is served cache-first and CACHE_VERSION had sat at v1 through four commits that changed main.js, so a returning reader kept the old bundle: none of the new UI reached them and the page looked simply unchanged. sw.js says to bump it on any shell change and I did not. Also tells the reader why the game list holds only tracked games when they have none of their own yet — the list is nine games we cover with no hint that a game of theirs has to exist before an event can be filed under it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-17 18:34:34 +02:00
Lucas WintherandClaude Opus 5	b86794a62d	feat: add GitHub Actions CI and support hosting under a subpath ... Mirrors the GitLab pipeline — typecheck, tests, feed sanity — and adds a Pages deploy. Pages serves from /<repo>/, and the app used absolute asset paths, so that job would have shipped a site that 404s on everything. Assets now resolve against a <base href> the build substitutes, the feed URL resolves against document.baseURI so deep links work too, and the service worker derives its paths from its own registration scope. Root-hosted builds are unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-15 01:22:22 +02:00
Lucas WintherandClaude Opus 5	c633d0510d	feat: work offline ... The reader's question is answered entirely by data already on the device and countdowns run off the local clock, so losing signal should not lose the app. The shell is cache-first; the feed is network-first falling back to the last copy seen, because stale events beat a blank screen. Webfonts are cached too — without them an offline load silently drops to system faces and the whole thing changes character. Offline is surfaced in the header and above the footer rather than hidden: stale data must never be presented as current. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-15 00:52:41 +02:00