/* ==========================================================================
   Xphias LLC Guest Speaker Manager
   03-chrome.css
   App chrome: side panel, options panel, menus and docks.
   ========================================================================== */

#side-panel-overlay.show {
  display: block;
}
#roster-dock-btn {
  position: fixed;
  top: 50%;
  left: 0;
  transform: translateY(-50%);
  background: var(--navy2);
  border: 1.5px solid var(--brand);
  border-left: none;
  color: var(--brand);
  padding: 14px 7px;
  border-radius: 0 8px 8px 0;
  cursor: pointer;
  z-index: 400;
  writing-mode: vertical-rl;
  text-orientation: mixed;
  font-size: 11px;
  font-weight: 800;
  letter-spacing: 1.5px;
  box-shadow: 4px 0 15px rgba(0,0,0,0.5);
  display: flex;
  align-items: center;
  gap: 6px;
  transition: all 0.25s ease;
}
#roster-dock-btn:hover {
  background: var(--brand);
  color: #000;
  transform: translateY(-50%) translateX(3px);
}
#side-panel.open ~ #roster-dock-btn {
  opacity: 0;
  pointer-events: none;
}

#options-panel {
  position: fixed;
  top: 0;
  right: 0;
  width: min(350px, 85vw);
  height: 100vh;
  background: var(--navy);
  border-left: 2px solid var(--brand);
  box-shadow: -10px 0 35px rgba(0, 0, 0, 0.75);
  display: flex;
  flex-direction: column;
  z-index: 1000;
  transform: translateX(100%);
  transition: transform 0.32s cubic-bezier(0.16, 1, 0.3, 1);
}
#options-panel.open {
  transform: translateX(0);
}

/* The menu list itself. These five lines were inline on the tag until
   1.55.0, where they quietly made the two-column rule below impossible:
   an inline style beats a stylesheet, so display:flex won every time. */
.opt-menu-list {
  flex: 1;
  overflow-y: auto;
  padding: 12px;
  display: flex;
  flex-direction: column;
  gap: 8px;
}

/* TWO COLUMNS, ONCE THERE IS ROOM FOR TWO.

   The menu grew to seventeen rows and a single column of seventeen is a
   scroll on every screen in the building -- which means the row you want is
   usually the one just out of sight, and the drawer stops being a menu and
   becomes a list to read. Two columns fit the whole thing at once on a
   desktop, which is the only arrangement where "where is X" is answered by
   looking rather than scrolling.

   Kept to one column below 1024px on purpose. Two columns of these rows on
   a laptop half-screen or a tablet would be two columns of truncated
   descriptions, and a row whose description is cut off is worse than a row
   you have to scroll to. The drawer widens only when the screen can carry
   it. */
@media (min-width: 1024px) {
  #options-panel { width: min(720px, 92vw); }
  #options-panel #options-menu-list {
    display: grid;
    grid-template-columns: 1fr 1fr;
    align-content: start;
  }
}

/* The nudge on hover slid rows sideways, which in two columns moves them
   towards their neighbour rather than out of a flush edge. Lifted instead:
   same amount of movement, no collision. */
@media (min-width: 1024px) {
  #options-panel .opt-item:hover { transform: translateY(-2px); }
}
#options-panel-overlay {
  display: none;
  position: fixed;
  inset: 0;
  background: rgba(0, 0, 0, 0.65);
  backdrop-filter: blur(3px);
  z-index: 999;
}
#options-panel-overlay.show {
  display: block;
}

@keyframes gentleFadeInOut {
  0%, 100% {
    opacity: 1;
    border-color: var(--cyan);
    box-shadow: 0 0 12px rgba(0, 180, 216, 0.4);
  }
  50% {
    opacity: 0.45;
    border-color: rgba(0, 180, 216, 0.2);
    box-shadow: 0 0 2px rgba(0, 180, 216, 0.1);
  }
}
.animate-fade-pulse {
  animation: gentleFadeInOut 2.5s ease-in-out infinite;
}

.opt-item {
  background: var(--navy2);
  border: 1px solid var(--c-border);
  border-radius: 6px;
  padding: 10px 12px;
  cursor: pointer;
  display: flex;
  align-items: center;
  gap: 12px;
  transition: all 0.2s ease;
  user-select: none;
}
.opt-item:hover {
  background: rgba(0, 180, 216, 0.1);
  border-color: var(--cyan);
  transform: translateX(-3px);
}
.opt-icon {
  width: 34px;
  height: 34px;
  background: rgba(255, 255, 255, 0.05);
  border: 1px solid var(--c-border);
  border-radius: 6px;
  display: flex;
  align-items: center;
  justify-content: center;
  font-size: 16px;
  flex-shrink: 0;
  color: var(--brand);
  transition: border-color 0.2s;
}
.opt-item:hover .opt-icon {
  border-color: var(--cyan);
  color: var(--cyan);
}
.opt-text {
  flex: 1;
  min-width: 0;
}

/* ==========================================================================
   THE TITLE BAR
   --------------------------------------------------------------------------
   Five words on a button is fine on a wide screen and ruinous on a narrow
   one. Rather than dropping controls at small sizes, the labels retire and
   the icons stay: every button is still there, still in the same order, and
   every one keeps a tooltip saying what it is.
   ========================================================================== */
.tb-btn {
  display: inline-flex; align-items: center; gap: 6px;
  white-space: nowrap; flex: 0 0 auto;
}
#btn-search-editor, #btn-help-editor, #btn-options-editor {
  border-color: var(--cyan); color: var(--cyan);
}
#btn-roster-toggle { border-color: var(--brand); color: var(--brand); }

/* The 6px left margin was here to hold the title off the Home button that
   used to sit before it. The title leads the bar now, so the margin was
   pushing it off the edge it is supposed to start at. */
.toolbar-title-box {
  display: flex; align-items: center; gap: 10px;
  margin-left: 0; min-width: 0;
}

.tb-logo {
  width: 36px; height: 36px; flex-shrink: 0;
  display: flex; align-items: center; justify-content: center;
  border-radius: 5px; overflow: hidden;
}
.tb-logo img { width: 100%; height: 100%; object-fit: contain; display: block; }

/* What you get when images/x.png is not on the server. The lettermark
   replaces the image inside the box, so it fills whatever the box is. */
.tb-logo .tb-logo-letter {
  width: 100%; height: 100%;
  display: flex; align-items: center; justify-content: center;
  border-radius: 5px;
  background: var(--brand); color: #000;
  font-weight: 800; font-size: 17px; line-height: 1;
}

/* THE NAME BLOCK: Curator, what it does, who made it.

   THE NAME IS THE TITLE, AND IT BEHAVES LIKE ONE.

   It used to be pinned at 18pt. One fixed number cannot be right on a
   phone and on a 27-inch monitor at the same time: at 18pt it was a
   caption on the big screen and it still crowded the small one. So the
   size is now a range with a rule for getting between the two ends:

       clamp(25px, 1.15vw + 13px, 32px)
              |         |     |     |
              |         |     |     the most it will ever be
              |         |     the part that does not move, so it never
              |         |     collapses to nothing on a narrow screen
              |         grows by just over a hundredth of the window
              the least it will ever be

   On a phone it settles at 25px; by a 1440px laptop it is about 30px; on
   a wide monitor it stops at 32px and refuses to get any bigger, because
   a title that keeps growing stops being a title and becomes a banner.
   Nothing steps or jumps -- drag the window and the name grows with it.

   A browser too old for clamp() reads the plain 26px line above it and
   ignores the clamp line entirely, which is the point of writing both.

   The strapline and the credit are sized FROM the name rather than set on
   their own, so the block always holds the same proportions -- and they
   have ceilings of their own, so growing the name never turns the small
   print into a second headline.

   The colours are the theme's own tokens, not fixed values, so the block
   follows every palette the app ships with: the name in the brand colour,
   the line under it in cyan, the credit in the muted grey. */
.tb-title-text {
  min-width: 0;
  --tb-title-size: 26px;                             /* the old browser's answer */
  --tb-title-size: clamp(25px, 1.15vw + 13px, 32px); /* everybody else's */
}
.tb-title-text h1,
.tb-title-text .tb-app-name {
  font-size: 26px;
  font-size: var(--tb-title-size);
  color: var(--brand); margin: 0; line-height: 1.05;
  font-weight: 800; letter-spacing: .4px;
  white-space: nowrap; overflow: hidden; text-overflow: ellipsis;
}
.tb-title-text .tb-app-what {
  font-size: 11px;
  font-size: clamp(10px, calc(var(--tb-title-size) * .40), 13px);
  color: var(--cyan); margin: 0; line-height: 1.25;
  font-weight: 600; letter-spacing: .2px;
  white-space: nowrap; overflow: hidden; text-overflow: ellipsis;
}
.tb-title-text .tb-app-who {
  font-size: 8px;
  font-size: clamp(8px, calc(var(--tb-title-size) * .30), 10px);
  color: var(--muted); margin: 0; line-height: 1.3;
  letter-spacing: .3px;
  white-space: nowrap; overflow: hidden; text-overflow: ellipsis;
}
.tb-title-text p {
  font-size: 6pt; color: var(--muted); margin: 0;
  white-space: nowrap; overflow: hidden; text-overflow: ellipsis;
}

/* Labels retire first, because an icon with a tooltip still works. */
@media (max-width: 1320px) {
  .toolbar-right .tb-lbl { display: none; }
  .toolbar-right .tb-btn { gap: 0; padding-left: 11px; padding-right: 11px; }
  /* Add a Speaker keeps its words longest: it is the one thing on this bar
     somebody may be looking for without knowing the icon. */
  .toolbar-right .btn-add-speaker .tb-lbl { display: inline; }
  .toolbar-right .btn-add-speaker { gap: 6px; }
}
@media (max-width: 1080px) {
  .toolbar-right .btn-add-speaker .tb-lbl { display: none; }
  .toolbar-right .btn-add-speaker { gap: 0; }
}
/* THE NAME NEVER GOES.

   The whole block used to be hidden below 760px, leaving the lettermark on
   its own -- and a square with an X in it is not the name of anything. The
   two small lines under it are what gets given up on a narrow screen, one
   at a time, least important first: the credit, then the strapline. CURATOR
   itself stays at every width, which is what a title is for. */
@media (max-width: 1080px) {
  .tb-title-text .tb-app-who { display: none; }
}
@media (max-width: 900px) {
  .tb-title-text .tb-app-what { display: none; }
}
@media (max-width: 760px) {
  .toolbar-left .tb-lbl { display: none; }
  .toolbar-left .tb-btn { gap: 0; padding-left: 11px; padding-right: 11px; }
}


/* ==========================================================================
   THE ROSTER DRAWER, IN TWO COLUMNS

   The cards fill LEFT TO RIGHT, row by row, in whatever order the Sort box
   is set to -- so with the default "Upcoming / Recent Engagement" the most
   recent appearance is top-left and it reads across, then down, the way a
   page does. grid-auto-flow is left at row for exactly that reason: column
   flow would fill the whole left-hand side first and put the second name in
   the list at the bottom of the screen.

   align-items: start stops a short card being stretched to the height of a
   tall one beside it, which is what "proportionally" asks for -- each card
   is as tall as its own contents.
   ========================================================================== */
.sb-list-2col {
  display: grid;
  grid-template-columns: repeat(auto-fill, minmax(280px, 1fr));
  gap: 8px;
  align-items: start;
  align-content: start;
}

/* The drawer's own header spans whatever the grid is doing. */
.sb-list-2col > .sb-section-head,
.sb-list-2col > .sb-empty {
  grid-column: 1 / -1;
}


/* ==========================================================================
   THE OPTIONS DOCK, OPPOSITE THE ROSTER DOCK

   Same tab, same height, same behaviour, mirrored to the right-hand edge --
   so the two drawers are opened the same way and you do not have to
   remember that one of them is only in the title bar.
   ========================================================================== */
#options-dock-btn {
  position: fixed;
  top: 50%;
  right: 0;
  left: auto;
  transform: translateY(-50%);
  background: var(--navy2);
  border: 1.5px solid var(--brand);
  border-right: none;
  color: var(--brand);
  padding: 14px 7px;
  border-radius: 8px 0 0 8px;
  cursor: pointer;
  z-index: 400;
  writing-mode: vertical-rl;
  text-orientation: mixed;
  font-size: 11px;
  font-weight: 800;
  letter-spacing: 1.5px;
  box-shadow: -4px 0 15px rgba(0,0,0,0.5);
  display: flex;
  align-items: center;
  gap: 6px;
  transition: all 0.25s ease;
}
#options-dock-btn:hover {
  background: var(--brand);
  color: #000;
  transform: translateY(-50%) translateX(-3px);
}
/* Out of the way while its own drawer is open, exactly as the roster tab is.
   The panel is not a sibling of this button, so the state is put on <body>
   by toggleOptions() rather than matched with a combinator. */
body.options-open #options-dock-btn {
  opacity: 0;
  pointer-events: none;
}


/* ==========================================================================
   THE TITLE BAR, LESS CROWDED

   It had grown to eight controls plus a title block and two badges, which
   on a 13-inch laptop wrapped to two rows. Three changes, none of which
   removes anything:

   1. THE NAME AND THE MODE SHARE A LINE. The badge used to sit after the
      whole title block; it is now beside CURATOR, where the app's name and
      the app's state read as one thing.

   2. THE LABELS GO SOONER. Home, Sign In, Help, Options, Save and PDF are
      all icons with tooltips from 1180px down, rather than 1320px. New
      Speaker keeps its words longest because it is the one control somebody
      may be looking for without knowing the icon.

   3. SAVE AND PDF GO QUIET. They are outline buttons at rest and colour on
      hover, so the bar has ONE coloured button — New Speaker — instead of
      three competing for the eye.
   ========================================================================== */
.tb-name-row {
  display: flex;
  align-items: center;
  gap: 10px;
  min-width: 0;
}
.tb-name-row .tb-app-name { flex: 0 0 auto; }
/* Smaller here than it is alone: beside an 18pt name a full-size badge is
   a second headline. */
.tb-mode {
  font-size: 7pt !important;
  padding: 2px 7px !important;
  letter-spacing: .4px;
  white-space: nowrap;
  flex: 0 0 auto;
}

/* The gold PDF button was the brightest thing on the bar and it is the one
   people press least. Gold on hover, outline at rest. */
.toolbar-right #btn-generate-pdf {
  background: transparent;
  border: 1px solid var(--brand);
  color: var(--brand);
}
.toolbar-right #btn-generate-pdf:hover {
  background: var(--brand);
  color: #000;
}

@media (max-width: 1180px) {
  .toolbar-right .tb-lbl,
  .toolbar-left .tb-lbl { display: none; }
  .toolbar-right .tb-btn,
  .toolbar-left .tb-btn { gap: 0; padding-left: 11px; padding-right: 11px; }
  .toolbar-right .btn-add-speaker .tb-lbl { display: inline; }
  .toolbar-right .btn-add-speaker { gap: 6px; }
}

/* The strapline and the credit are dropped by the two rules further up
   (1080px for the credit, 900px for the strapline), so there is nothing to
   repeat here. The name itself is never hidden at any width. */


/* ==========================================================================
   THE PROFILES ROSTER, IN TWO COLUMNS

   WHAT WAS WRONG

   1. The card carried `margin-bottom: 10px` from when the list was a stack.
      Inside a grid with an 8px gap that ADDS: 18px between rows against 8px
      between columns, so nothing lined up and the whole thing read as
      ragged rather than gridded.

   2. The speaker's name and four action buttons shared one row. The buttons
      need about 130px; at half of a 660px drawer the column is ~300px, so
      "Rev. Dr. William Holmes Robinson" was left with 160px and the two
      sides ran into each other. That is the overlap.

   3. Every card was a different shape inside, because the number of lines
      in the name block varied. Two cards side by side had nothing in common
      to line up ON.

   WHAT IT IS NOW

   Three bands, the same in every card: NAME (the whole column to itself),
   ACTIONS (their own row, right-aligned), APPEARANCES. Cards sit in the
   grid at their natural height with one gap value in both directions, and
   because the bands are in the same order in every card the eye reads rows
   across as well as columns down.
   ========================================================================== */
#sb-list.sb-list-2col {
  gap: 10px;
  align-content: start;
  /* grid-auto-rows: min-content IS THE FIX FOR THE OVERLAP.

     #sb-list is flex:1 inside a 100vh drawer, so the grid has a DEFINITE
     height. An `auto` row in a grid that has been given a definite height
     is stretched to share that height out -- five rows of 165px here --
     and a card taller than its row simply overflows into the one below.
     That is what "junky and overlapping" was: the tallest cards sitting on
     top of the cards underneath them.

     align-items and align-content control where an item sits IN its row;
     neither changes how tall the row is, which is why setting them to
     start did not help. min-content sizes the row to its contents, so a
     card with five appearances gets the height it needs and the card below
     it starts underneath.

     Measured before and after: rows went from a flat 165px each to
     413 / 166 / 228 / 228 / 166 -- the real heights of the cards in them. */
  grid-auto-rows: min-content;
}

/* ---- Band one: who ------------------------------------------------------ */
.roster-card .rc-top {
  padding: 10px 12px 8px;
  cursor: pointer;
  background: rgba(255, 255, 255, .02);
  min-width: 0;
}
.roster-card .rc-top:hover { background: rgba(255, 255, 255, .05); }

/* The name gets the full width and wraps to a second line rather than being
   cut off. A roster you cannot read the names in is not a roster. */
.rc-name {
  font-weight: 700;
  font-size: 12px;
  line-height: 1.3;
  color: #fff;
  overflow-wrap: anywhere;
  display: -webkit-box;
  -webkit-line-clamp: 2;
  -webkit-box-orient: vertical;
  overflow: hidden;
}
.roster-card.active .rc-name { color: var(--cyan); }

.rc-org {
  font-size: 10px;
  color: var(--muted);
  margin-top: 1px;
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}

/* The counts. The NUMBER is the thing you scan for, so it stays while the
   word after it retires on a narrow column -- "5 appearances" becomes "5". */
.rc-stats {
  display: flex;
  align-items: baseline;
  gap: 5px;
  margin-top: 4px;
  font-size: 9px;
  color: var(--muted);
}
.roster-card.active .rc-stats { color: var(--cyan); }
.rc-stat { font-weight: 700; white-space: nowrap; }
.rc-stat i { font-style: normal; font-weight: 400; }
.rc-dot { opacity: .5; }

/* ---- Band two: what you can do ------------------------------------------ */
/* Its own row, right-aligned, with a hairline above it so it reads as a
   footer for the name rather than as another line of information. */
.roster-card .roster-actions {
  display: flex;
  justify-content: flex-end;
  gap: 2px;
  margin: 0;
  padding: 4px 8px;
  border-top: 1px solid rgba(255, 255, 255, .05);
  background: rgba(0, 0, 0, .12);
}
.roster-card .roster-actions button {
  width: 26px;
  height: 24px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  font-size: 12px;
  padding: 0;
}

/* ---- Band three: when --------------------------------------------------- */
.rc-occ-name {
  font-size: 10.5px;
  font-weight: 600;
  margin-top: 2px;
  overflow-wrap: anywhere;
  display: -webkit-box;
  -webkit-line-clamp: 1;
  -webkit-box-orient: vertical;
  overflow: hidden;
}
.rc-occ-title {
  font-size: 9.5px;
  color: var(--cyan);
  margin-top: 1px;
  line-height: 1.35;
  display: -webkit-box;
  -webkit-line-clamp: 2;
  -webkit-box-orient: vertical;
  overflow: hidden;
  overflow-wrap: anywhere;
}
.rc-occ-ref { color: var(--muted); }

/* ---- One column: the words come back ------------------------------------ */
/* Below two columns there is room for the full labels again, and the card
   goes back to reading like a row. */
@media (max-width: 760px) {
  .rc-name { -webkit-line-clamp: 3; }
}

/* NOTE: an earlier draft of this used a container query to drop the words
   from "5 appearances" in a narrow column. Container queries are not on the
   older iPads in the booth, so it is gone: the stats line is short, the name
   has its own row now, and there is room for the words at every width this
   drawer reaches. */


/* ==========================================================================
   ON A PHONE, THE BUTTONS SAY WHAT THEY ARE

   Every rule above this one takes words away as the window narrows, which
   is right on a laptop: the bar is one row, the row has to fit, and an icon
   with a tooltip is a fair trade for the space.

   A phone is not that. The bar is not one row there -- it already stacks
   (css/02-layout.css) and it can have as many rows as it needs, because the
   page scrolls. What it cannot afford is a row of unlabelled 16px glyphs:
   there is no tooltip on a touch screen, so an icon with its words taken
   away is an icon nobody can identify without pressing it to find out.

   So below 768px every label comes back, each button becomes an icon over
   its own word, and they wrap onto as many lines as they need. Two per row
   at phone widths, three once there is room, and each one at least 44px
   tall, which is the size a thumb actually hits.

   This block is last in the file on purpose. It has to out-rank the four
   label-hiding queries above it, and being last is how it does that without
   a single !important.
   ========================================================================== */
@media (max-width: 768px) {

  /* The words come back. All of them, on both sides of the bar. */
  .toolbar-right .tb-lbl,
  .toolbar-left .tb-lbl,
  .toolbar-right .btn-add-speaker .tb-lbl {
    display: block;
    font-size: 9.5px;
    font-weight: 700;
    line-height: 1.15;
    letter-spacing: .2px;
    white-space: normal;       /* two short words may stack; that is fine */
    text-align: center;
  }

  /* Icon on top, word underneath. A 15px glyph over 9.5px words reads at
     arm's length; the same two side by side does not fit two to a row. */
  .toolbar-right .tb-btn,
  .toolbar-left .tb-btn,
  .toolbar .btn {
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    gap: 3px;
    padding: 7px 6px;
    min-height: 46px;          /* a thumb, not a cursor */
    font-size: 15px;           /* the glyph */
    line-height: 1.1;
    border-radius: 7px;
  }

  /* As many rows as it takes. Two across on a small phone, three once the
     screen is wide enough for them, and nothing ever pushed off the edge. */
  .toolbar-right {
    display: flex;
    flex-wrap: wrap;
    justify-content: stretch;
    gap: 6px;
    width: 100%;
  }
  .toolbar-right .tb-btn,
  .toolbar-right .btn {
    flex: 1 1 calc(50% - 6px);
    min-width: 104px;
  }
  /* The left-hand side holds the name, so its buttons sit in a row of their
     own underneath rather than fighting the title for the same line. */
  .toolbar-left {
    flex-wrap: wrap;
    row-gap: 6px;
  }
  .toolbar-left .tb-btn,
  .toolbar-left .btn {
    flex: 1 1 calc(50% - 6px);
    min-width: 104px;
  }
  .toolbar-left .toolbar-title-box {
    flex: 1 1 100%;            /* CURATOR gets the whole first row */
  }

  /* One coloured button on the bar is the rule everywhere else and it holds
     here: New Speaker stays gold, the rest stay quiet. */
  .toolbar-right #btn-generate-pdf,
  .toolbar-right #btn-export-excel {
    width: auto;
    min-width: 0;
  }
}

/* Three across once the phone is wide enough to read three words on a line.
   Written as its own top-level query rather than nested inside the one
   above, because nested @media is only a couple of years old in browsers
   and an older iPad would simply throw the whole block away. */
@media (min-width: 480px) and (max-width: 768px) {
  .toolbar-right .tb-btn,
  .toolbar-right .btn {
    flex: 1 1 calc(33.333% - 6px);
  }
}


/* ==========================================================================
   AN ARCHIVED CARD CARRIES A FACE, NOT A COUNTDOWN

   The portrait is what makes a row of archived appearances scannable. The
   ring and the figure are deliberately absent: they measure time until an
   event, and an archived event is not coming. Restoring one puts both back,
   because the active card builds them from the same picture.
   ========================================================================== */
.roster-card.archive-card .roster-card-header {
  display: flex; align-items: flex-start; gap: 10px;
}
.arch-face { flex: 0 0 auto; line-height: 0; }
.arch-face .speaker-portrait {
  width: 46px; height: 46px;
  border-radius: 50%;
  border: 1.5px solid var(--c-border);
  box-shadow: none;
  filter: saturate(.75);      /* put away, not deleted */
}
/* Belt and braces: if a ring ever reaches this list, it does not draw. */
.roster-card.archive-card .xp-pring-svg,
.roster-card.archive-card .xp-pring-pct { display: none !important; }


/* ==========================================================================
   HELP, SIGN IN AND OPTIONS INSIDE A FULL-SCREEN MODAL
   --------------------------------------------------------------------------
   The Event Calendar and the Analytics Hub cover the toolbar, so they carry
   their own copy of its last three controls, immediately left of the ✕.
   Built by js/68-modalchrome.js; styled to read as the same buttons, because
   they are the same buttons.
   ========================================================================== */
.mc-cluster {
  display: flex;
  align-items: center;
  gap: 8px;
  flex-wrap: wrap;
}
.mc-btn {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 6px 12px;
  font-size: 10.5px;
  min-height: 32px;
  white-space: nowrap;
}
.mc-btn .tb-ico { font-size: 12px; line-height: 1; }
.mc-btn .tb-lbl { letter-spacing: .3px; }

/* Signed in, so this one is the way OUT. Same signal the toolbar uses. */
.mc-btn.is-out { border-color: rgba(239, 68, 68, .55); color: #fca5a5; }
.mc-btn.is-out:hover { border-color: var(--red); color: #fff; }

/* THE OPTIONS DRAWER HAS TO BE ABOVE THE MODAL THAT OPENED IT.

   It was z-index 1000, which is below the Event Calendar (5000) and the
   Analytics Hub (8000) -- so pressing Options from inside either one opened
   the drawer BEHIND it and looked like the button did nothing. Raised above
   both, and above the ordinary dialog at 9999, but still below the welcome
   box, which is modal in the real sense and must not be reachable past. */
#options-panel { z-index: 10050; }
#options-panel-overlay { z-index: 10040; }

/* On a narrow screen the words go and the icons stay -- three labels plus a
   heading plus a ✕ do not fit across a phone, and an icon that has always
   meant Options still means Options. */
@media (max-width: 860px) {
  .mc-btn { padding: 6px 9px; }
  .mc-btn .tb-lbl { display: none; }
}

/* Nothing in this cluster belongs on paper. */
@media print {
  .mc-cluster { display: none !important; }
}
