Admin
94a1981a4c
Dark mode's accent chroma came from the ACCENT_CHROMA constant (0.145, originally meant as a generic default), used unconditionally for every accent-derived token regardless of the actual song's extracted vividness - extractAccent() already clamps a song's real chroma to 0.045-0.11, but buildThemeTokens() never used it, only the hue. That made every accent button, ring and highlight uniformly vivid. Drop it to 0.09. Also soften --mf-accent-title (the accent-colored track title text, e.g. active rows) from 0.07 to 0.05 chroma, since that was called out specifically as too strong. Cleaned up the now-unused C/ACCENT_CHROMA import.
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.