/* ======================================
   RAIDA PROTOCOL THEME OVERRIDES
   Loaded after styles.css only on pages
   under /protocol/. Redefines the global
   color tokens, so any rule that uses
   var(--primary-bg) etc. repaints itself.
   ====================================== */

:root {
  /* Dark purple palette */
  --primary-bg:   #1a0d2e;   /* deep dark purple (page background) */
  --secondary-bg: #2a1845;   /* mid purple (cards, sidebar items) */
  --tertiary-bg:  #20103a;   /* between primary and secondary */
  --overlay-bg:   rgba(20, 6, 40, 0.65);
  --border-color: rgba(200, 170, 255, 0.18);

  /* Link / accent colors tuned for a purple background */
  --accent-blue:  #c8a8ff;   /* lavender — used for links and headers */
  --accent-green: #ffd27a;   /* warm amber — secondary link color */
  --text-primary: #f5edff;
  --text-secondary: #d8c9f0;
  --text-muted: rgba(245, 237, 255, 0.78);
}

/* Anchor color: the inline a {color:#ba6} from protocol-common-styles.php
   targets <a> elements directly, beating the variable. Bump specificity so
   the lavender wins on protocol pages. */
.content a,
.content a:visited,
main.content a,
main.content a:visited {
  color: var(--accent-blue);
}

.content a:hover,
main.content a:hover {
  color: #ffd27a;
}

/* Inline <code> chips read better with a touch more contrast on the
   purple background. */
code {
  background-color: rgba(0, 0, 0, 0.35);
  color: #f3e6ff;
}

/* Page background safety net: some layouts paint <body> with a fixed
   color rather than the variable. Force the purple. */
body {
  background-color: var(--primary-bg);
}
