feat(booking): give the booking flow a dark palette derived from its own colours

components/appointment/ had every colour hard-coded, so the flow rendered identically in either theme even after the wiring was fixed. It now reads from CSS custom properties. These are not new colours. The :root values are byte-for-byte the hex codes that were already in the components — twenty-one files, mapped one to one — so light mode is unchanged. The dark values are derived from those same colours: surfaces and borders darkened, text inverted, and the two brand colours (the indigo and the orange) lightened rather than replaced, because both lose contrast against a dark surface at their original values. Verified in a headless browser with prefers-color-scheme forced dark: data-theme lands on <html> and --ap-surface resolves to #1b1b20 rather than white. Six one-off colours remain hard-coded — a success green, an error red and similar — each used exactly once and none of them a surface. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-01 16:33:39 +03:30
parent 2fb17d778a
commit 51c21938eb
22 changed files with 149 additions and 95 deletions
@@ -3,7 +3,7 @@ import SelectDatePicker from "./SelectDatePicker";
 function Time({ isStep, setDate, disabledDates, clinicUuid }) {
  return (
    <div className="flex relative mt-[24px] flex-col items-start gap-[19px] justify-start">
-      <p className="text-[#3B3B3B] text-[14px] md:text-[16px] font-bold">
+      <p className="text-[var(--ap-text)] text-[14px] md:text-[16px] font-bold">
        1. انتخاب روز
      </p>
      <SelectDatePicker setDate={setDate} disabledDates={disabledDates} clinicUuid={clinicUuid} />