Dark Reader inverts an already-dark palette, which wrecks the interface: the
colours here carry meaning — the urgency ramp is how you read how soon
something ends — so having them re-mapped is not a cosmetic problem.
darkreader-lock is its documented opt-out. color-scheme: dark is the standard
signal alongside it, so browser chrome and form controls render dark too.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
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) <[email protected]>
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) <[email protected]>
Tailwind v4 @theme carries the two colour axes as tokens: a deep blue-black
ground, per-game hues for identity, and a heat ramp for urgency that is
monotonic in salience (dim, blue, amber, red).
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Lucas Winther