fabi
da2d4f67e7
Some checks failed
Audit / cargo audit (backend) (push) Failing after 9m40s
E2E / Cross-UA smoke matrix (push) Has been cancelled
E2E / Playwright E2E (chromium + webkit) (push) Has been cancelled
Audit / npm audit (frontend) (push) Has been cancelled
Checks / Backend — cargo test + clippy + fmt (push) Has been cancelled
Checks / Frontend — vitest + svelte-check (push) Has been cancelled
Checks / Keepsake viewer — builds, self-contained, committed artifact in sync (push) Has been cancelled
Checks / E2E — typecheck + lint (push) Has been cancelled
The event is a wedding, so the camera icon becomes two interlocking bands. Drawn rather than sourced: at 16px in a tab anything finer than the stroke turns to smudge, which is why the camera it replaces was three shapes and no more. White on #8a6a2b, the event's own theme_primary, so the icon, the site and the PWA chrome finally agree -- the manifest's theme_color was still the #2563eb from the camera branding. The rings span x 88-424 and y 139-373 including stroke, inside the centre-80% safe zone, so an Android circle crop cannot clip them. Also removes a second, competing icon declaration. `+layout.svelte` imported `$lib/assets/favicon.svg` -- the orange Svelte logo from the project skeleton, which Vite inlined as a data URI into the layout bundle -- and applied it via `<svelte:head>`. Which of the two won was left to the browser: the link in app.html is parsed from the initial HTML, this one is added at hydration, and Chrome keeps the former. So the skeleton logo did not usually show, but nothing guaranteed that, and `ssr = false` means the branded link is the only one present at first paint anyway. app.html is now the single source and the skeleton asset is gone.
