Kristian WindandClaude Opus 5
2a3367bfe0
Release / Build and publish image (push) Failing after 13m28s
Every label link in the sidebar was dead. The route file landed in web/web/src/routes/ because the shell that created it was already inside web/ — SvelteKit never saw it, so /etiket/<name> fell through to the app shell and rendered nothing. The manifest also listed icon-192.png and icon-512.png, and app.html an apple-touch-icon, none of which were ever generated. A manifest pointing at missing icons is worse than one listing only what exists, so the dead references are gone and the SVG — which Chrome and Firefox install from happily — is what remains. docs: hand over the project HANDOFF.md covers what cannot be read out of the code: why the name is not skuld, the decisions that look strange until you know the reason, what is tested against a real service and what is only tested against its specification, the gaps in the order I would take them, and the traps that cost the most time to find. Co-Authored-By: Claude Opus 5 <[email protected]>
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