Kristian WindandClaude Opus 5
2300f1dc3b
Adding three themes meant measuring them, and measuring them meant measuring the two that shipped. They came last. --ink-faint is the tier that decides whether an interface is readable: dates, counts, hints and placeholders all live there, and it is the first thing to disappear. Dark sat at 3.8:1 against its ground and light at 3.1:1, where AA asks for 4.5. Light's accent — which is text as often as it is a background, on links and on "open the project" — sat at 3.8:1 too. All five now clear 4.5:1 at every tier. The numbers are in the code beside the colours, because the next person to nudge a hex should measure rather than look: this is exactly the kind of change that looks fine to whoever makes it. Left alone earlier today as a deliberate scope call — recolouring somebody's app as a side effect of adding themes is not a side effect anyone asked for — and done now that it was asked for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
web
The SvelteKit PWA. Not written yet — this directory holds its place so the Docker build has something to copy, and so the frontend stage can tell "not built yet" apart from "the build failed".
The Dockerfile builds this directory when it finds a package.json here, and
otherwise emits a placeholder page. So adding the real app is exactly: put a
SvelteKit project in this directory whose npm run build produces build/.
What it needs to be
- SvelteKit,
adapter-static, output inbuild/. The Go binary embeds that directory at compile time and serves it, falling back toindex.htmlso client-side routes survive a reload. - A PWA: installable, offline reading of already-cached lists, swipe gestures for complete and schedule.
- Nordic minimalism. Dark by default, light available. One accent colour, everything else neutral. Runic mark for Verdande.
- Optimistic on every local action. No spinner ever appears for something the browser could already know the answer to.
Talking to the backend
Same origin — the Go binary serves both. /api/v1 for REST, /api/v1/ws for the
live sync. Session cookie is httpOnly, so the frontend never handles the token
itself.
During development, run the backend on 8080 and point the Vite dev server's proxy at it:
VERDANDE_DATA_DIR=./data VERDANDE_DEV=true go run ./cmd/verdande