Admin
93d4220f3a
--mf-accent-soft-bg/--mf-accent-btn-bg/-hover were translucent alpha overlays, so an accent-tinted element (e.g. the active-row highlight, or the accent Button) rendered differently depending on what was already underneath it: fine over the plain page background, but over an already-tinted surface like the spotlight card, the two translucent layers stacked and the combined result read brighter/more saturated than intended. Same fix as bg-btn earlier: replace the alpha overlay with a solid color-mix() against --mf-bg, computed once, so the token always renders identically regardless of what it's placed on top of. Verified the active-row highlight and the accent button now compute to the exact same color whether they sit on the plain background or on the spotlight card.
web-player
Musify's web client: SvelteKit 2 (adapter-node), Svelte 5 runes, Tailwind 4,
TypeScript. Authentication is server-side OIDC against Zitadel (openid-client
and jose) with an encrypted session cookie; the backend is called from load
functions and form actions through a typed openapi-fetch client.
Development
npm install
npm run dev # :5173
Configuration lives in .env (template in .env.example). Bring the
infrastructure stack up first (see ../deploy/README.md)
and copy the WEB_CLIENT_ID / WEB_CLIENT_SECRET it writes to deploy/.env
into this .env once, then run the dev server.
npm run check # svelte-check — must be clean before closing a change
npm run lint # prettier --check . && eslint .
npm run format # prettier --write .
npm run build # production build into build/
npm run gen:api # regenerate src/lib/api/schema.d.ts from the running API
Production
Built and run as a container by the production stack — see
../deploy/README.md. There the same variables come from
deploy/.env.prod through compose instead of from .env.
Conventions and the design system are documented in CLAUDE.md and
in the musify-web skill.