Bug description
src/app/globals.css defines raw CSS custom properties --film-600 / --film-400 with literal hex values that differ between light (globals.css:19-20, #e63946/#ff6b6b) and dark (:65-66, #FF6666/#66FF66) mode. But tailwind.config.ts:22-34 completely overrides the film color scale used everywhere in components (text-film-600, border-film-400, etc.) to route through var(--accent) / var(--accent-hover) instead — a different variable entirely. A repo-wide grep confirms var(--film-*) is never actually referenced anywhere in src/.
Steps to reproduce
grep -n "film-600\|film-400" src/app/globals.cssgrep -n "film:" tailwind.config.tsgrep -rn "var(--film" src/ → zero results
Expected behavior
Either the raw --film-* variables are actually used somewhere and this is a latent theming bug waiting to surface, or they're dead code that should be removed to avoid confusing a future contributor who reasonably assumes --film-600 is what text-film-600 resolves to.
Actual behavior
Two parallel, disconnected definitions of "film-600" exist with different values; the CSS one is unused.
Related to the broader #673 "dark mode audit" issue, but this is a specific, immediately actionable finding rather than something a general audit would necessarily catch (it's dead code, not a rendering bug).
Bug description
src/app/globals.cssdefines raw CSS custom properties--film-600/--film-400with literal hex values that differ between light (globals.css:19-20,#e63946/#ff6b6b) and dark (:65-66,#FF6666/#66FF66) mode. Buttailwind.config.ts:22-34completely overrides thefilmcolor scale used everywhere in components (text-film-600,border-film-400, etc.) to route throughvar(--accent)/var(--accent-hover)instead — a different variable entirely. A repo-wide grep confirmsvar(--film-*)is never actually referenced anywhere insrc/.Steps to reproduce
grep -n "film-600\|film-400" src/app/globals.cssgrep -n "film:" tailwind.config.tsgrep -rn "var(--film" src/→ zero resultsExpected behavior
Either the raw
--film-*variables are actually used somewhere and this is a latent theming bug waiting to surface, or they're dead code that should be removed to avoid confusing a future contributor who reasonably assumes--film-600is whattext-film-600resolves to.Actual behavior
Two parallel, disconnected definitions of "film-600" exist with different values; the CSS one is unused.
Related to the broader #673 "dark mode audit" issue, but this is a specific, immediately actionable finding rather than something a general audit would necessarily catch (it's dead code, not a rendering bug).