chore: merge main into dev (the colours from PR #35)

[ronjalh]

Summary

Brings the colours into dev. They were merged directly into main by accident (PR #35, "set up css variables", whose base was main), so dev does not have them.

This is a merge of main into dev. It contains only what main has and dev does not:

• src/styles/variables.css: the colour palette, text colours, fonts, box settings, spacing and dark mode colours
• src/styles/global.css (empty for now)
• src/main.tsx: imports the two style files

These are 5 commits by @xenia_grib from PR #35. There are no conflicts, and nothing else from main is missing in dev.

Why

• The interface issues (Create Search page header #40–Add element variants list to element page #48) are built on dev, so they need the colour variables there.
• The README and a comment in src/index.css (in the shadcn/ui and Tailwind PR feat: set up Tailwind CSS, shadcn/ui and Lucide icons #53) refer to src/styles/variables.css, which dev does not have yet.
• It keeps main and dev from drifting apart, so the later merge of dev into main is clean.

Merge it as a merge commit

Use "Create a merge commit", not squash or rebase, so that the history of main and dev stays shared.

Known problems in variables.css (not changed here)

This PR does not change the file, but two things in it do not work as intended:

• --background-color is declared twice. The second value (#BDE981, the D-value green) wins and becomes the page background.
• The [data-theme="dark"] block is nested inside :root { … }, so it matches a descendant of the root and not the page itself. Dark mode does not apply as written.

They should be fixed in a separate PR by whoever owns the design.

Testing

npm run lint, npm run build and npm test pass on the merged result.

🤖 Generated with Claude Code

[anettkva]

good catch:)