/* Skye overlay CSS: the only CSS file added to the LibreChat image. Linked from index.html by overlay/Dockerfile.
   Colors and the font family come from interface.theme in librechat.yaml (rendered from bank.yaml, U3); this file holds what
   yaml cannot: the font files (@font-face) and at most 10 element rules (U5). */
@font-face { font-family: "Skye Sans"; font-style: normal; font-weight: 400; font-display: swap;
  src: url("/assets/fonts/plex-sans-latin-400.woff2") format("woff2"); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; }
@font-face { font-family: "Skye Sans"; font-style: normal; font-weight: 500; font-display: swap;
  src: url("/assets/fonts/plex-sans-latin-500.woff2") format("woff2"); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; }
@font-face { font-family: "Skye Sans"; font-style: normal; font-weight: 600 700; font-display: swap;
  src: url("/assets/fonts/plex-sans-latin-600.woff2") format("woff2"); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; }
@font-face { font-family: "Skye Sans"; font-style: normal; font-weight: 400; font-display: swap;
  src: url("/assets/fonts/plex-sans-arabic-400.woff2") format("woff2"); unicode-range: U+0600-06FF, U+0750-077F, U+08A0-08FF, U+FB50-FDFF, U+FE70-FEFF, U+200C-200F, U+2E3A-2E3B; }
@font-face { font-family: "Skye Sans"; font-style: normal; font-weight: 500; font-display: swap;
  src: url("/assets/fonts/plex-sans-arabic-500.woff2") format("woff2"); unicode-range: U+0600-06FF, U+0750-077F, U+08A0-08FF, U+FB50-FDFF, U+FE70-FEFF, U+200C-200F, U+2E3A-2E3B; }
@font-face { font-family: "Skye Sans"; font-style: normal; font-weight: 600 700; font-display: swap;
  src: url("/assets/fonts/plex-sans-arabic-600.woff2") format("woff2"); unicode-range: U+0600-06FF, U+0750-077F, U+08A0-08FF, U+FB50-FDFF, U+FE70-FEFF, U+200C-200F, U+2E3A-2E3B; }

/* Element rules. At most 10 (a test counts them); each names the screenshot finding it fixes. CSS never hides a feature (U6). */

/* Finding A1 (slice A screenshots, home screen with an Arabic assistant name): the welcome heading is a <p class="split-parent">
   with overflow hidden and a line height of 40px for 36px text, so Arabic letters are cut at the top and bottom (the word
   "مساعد" showed half). A taller line gives the letters room; it is still one line of text and nothing else moves. */
p.split-parent { line-height: 1.6; }  /* the element selector beats Tailwind's .sm\:text-4xl line height */

/* Finding AJ1 (Arabic text looks disconnected, new-chat.ar screenshots): the heading wraps every character in its own
   <span class="inline-block transform"> inside a word span (inline-block, dir=auto). Chromium shapes Arabic one box at a time,
   so each letter got its isolated form and nothing joined. The word spans are also bidi isolates, so Arabic words came out in
   reverse order and the gap sat on the wrong side. Plain inline spans with normal bidi let the browser shape and order the whole
   heading as one run. The per-letter slide (a transform) no longer applies to inline boxes; the fade stays. The word-gap span
   (inline style width 0.3em) stays inline-block, so lines can still break between words. */
p.split-parent span:not(.sr-only):not([style*="width"]) { display: inline; unicode-bidi: normal; }