/* ══ THE SIGN IN CONTROL, ON EVERY PAGE (11 Sep 2026) ═══════════════════════════════════════════
   Sign in used to live nowhere in the site header; it was added to the homepage first and then to
   every page, because a header that offers it on one page and not the others is the same
   inconsistency the Canada entry was.

   WHY THIS IS ITS OWN FILE. The site does not have one shared stylesheet. A university profile
   page carries a single inline <style> and links nothing; /sector-data/ links its own local
   styles.css; /executive/ links two sheets and carries four inline blocks. Putting these rules in
   any one of those reaches a fraction of the pages. One small file, linked once per page, reaches
   all of them and is one place to change.

   SPECIFICITY, NOT ORDER. Every rule here is written at `.nav a.nav-signin` — one class deeper
   than a bare `.nav a` so it beats the page's own nav styling, and shallower than the homepage's
   `body.has-hero .site-head .nav a.nav-signin`, which must win because that header sits on a
   photograph. So this file works wherever a page chooses to load it.
   ══ */

/* the default: a paper header, so the control is drawn in ink */
.nav a.nav-signin,
.site-nav a.nav-signin {
  border: 1px solid var(--rule-hairline, #CBC7BB);
  border-radius: 5px;
  padding: 4px 11px;
  color: var(--ink, #1D1B1A);
  font-weight: 600;
  transition: border-color .18s ease, background-color .18s ease;
}
.nav a.nav-signin:hover,
.site-nav a.nav-signin:hover {
  border-color: var(--rule, #A6A294);
  background: rgba(29, 27, 26, .04);
}
.nav a.nav-signin:focus-visible,
.site-nav a.nav-signin:focus-visible {
  outline: 2px solid var(--accent, #234C50);
  outline-offset: 2px;
}

/* the drawer row reads like every other row; the label class already carries that */
.drawer__nav a.drawer__signin .drawer__lbl { font-weight: 600; }

/* ⚠ THE DESKTOP NAV ALREADY OVERFLOWED AT 1024 BEFORE Sign in JOINED IT. Measured on the
   homepage: five items ran 781px inside a 1024px header, so the last one was already past the
   edge, and the header clips rather than scrolls — so nothing looked broken and the outbound link
   was simply unreachable at that width. Every page has now gained an item, so the fix travels
   with it.
   Below 1200 the outbound CoreBridge Advisory link comes out of the desktop row. It is the one
   item that leaves the site, and it stays in the drawer, where every item lives anyway. */
/* ⚠ NOT SCOPED TO .site-head. /executive/ puts its nav OUTSIDE that wrapper, so a selector
   anchored on it missed exactly the page whose header this rule was needed on: measured at 1024,
   its nav ran to 1087px inside a 1024px viewport. `.nav` and `.site-nav` exist only in the site
   header, so naming them alone is specific enough and reaches every page's arrangement. */
@media (max-width: 1199px) {
  .nav .nav-out,
  .site-nav .nav-out { display: none; }
}

/* ⚠ ONE PAGE CARRIES AN EXTRA CONTROL IN ITS HEADER ROW. /executive/ puts a 264px lookup between
   the wordmark and the nav, so its row ran 1062px inside a 1024px header BEFORE Sign in existed —
   38px over — and 1128px after. Hiding the outbound link was not enough there because the surplus
   is the lookup, not the nav.
   Below 1200 the lookup steps out of the header. It is a convenience control on a page that has
   its own search in the body, and a navigation row that cannot be reached is worth less than a
   shortcut that can be found one scroll down.  exists on that page alone, so this
   reaches nothing else. */
@media (max-width: 1199px) {
  .site-head__inner .ex-lookup { display: none; }
}