/* Citation Builder, Local Leads and Site Audit Summary - the form.
   Three views, one set of form components. Every selector below names all three.
   Adding a fourth means adding it to every selector here: a view the list does
   not name gets NONE of this and falls back to centred card defaults, which is
   how Site Audit Summary shipped looking nothing like its two siblings.
   ---------------------------------------------------------------------------
   Linked rather than inline in dashboard.html, because this view carries
   [data-res]: its result can be captured for the public share page, and the
   worker-served page cannot reach an inline <style> block.

   The form itself never leaves the view. Only the [data-res] subtree is
   captured, and that is built entirely from the shared .mvr-* Result Shell in
   mvr.css, which the share page already links. */

/* Citation Builder's form. .ci-runrow puts a 340px minimum on each
   field, which never fits this panel, so every field wrapped to its own
   line and five identical boxes stacked up with nothing to tell them
   apart. A grid with a 170px track goes two-up where there is room and
   one-up where there is not. */
#view-citations .cit-group, #view-localleads .cit-group, #view-siteauditsummary .cit-group { text-align:left; margin-top:16px; }
#view-citations .cit-group + .cit-group, #view-localleads .cit-group + .cit-group, #view-siteauditsummary .cit-group + .cit-group { margin-top:18px; padding-top:16px; border-top:1px solid var(--border); }
#view-citations .cit-glabel, #view-localleads .cit-glabel, #view-siteauditsummary .cit-glabel { display:flex; align-items:baseline; gap:8px; margin:0 0 3px; font-size:12px; font-weight:600; letter-spacing:.05em; text-transform:uppercase; color:var(--text-2); }
#view-citations .cit-ghint, #view-localleads .cit-ghint, #view-siteauditsummary .cit-ghint { margin:0 0 11px; font-size:11px; line-height:1.55; color:var(--text-3); }
#view-citations .cit-grid, #view-localleads .cit-grid, #view-siteauditsummary .cit-grid { display:grid; grid-template-columns:repeat(auto-fit,minmax(170px,1fr)); gap:10px; }
#view-citations .cit-f, #view-localleads .cit-f, #view-siteauditsummary .cit-f { display:flex; flex-direction:column; gap:5px; min-width:0; }
#view-citations .cit-f--wide, #view-localleads .cit-f--wide, #view-siteauditsummary .cit-f--wide { grid-column:1 / -1; }
#view-citations .cit-f > label, #view-localleads .cit-f > label, #view-siteauditsummary .cit-f > label { display:flex; align-items:baseline; gap:7px; font-size:11px; font-weight:500; color:var(--text-2); }
/* Required is marked on the field, not explained in a paragraph after
   the form. The optional group says so in its own heading. */
#view-citations .cit-req, #view-localleads .cit-req, #view-siteauditsummary .cit-req { font-size:10px; font-weight:600; letter-spacing:.05em; text-transform:uppercase; color:var(--brand-solid); }
#view-citations .cit-opt, #view-localleads .cit-opt, #view-siteauditsummary .cit-opt { font-size:10px; font-weight:500; letter-spacing:.05em; text-transform:uppercase; color:var(--text-3); }
/* flex:0 0 auto, and the height put back.

   .ci-field carries flex:1 for the row it was designed for, and flex:1 means
   flex-basis:0%. In a ROW that is a width basis and harmless. These sit in a
   flex-direction:column wrapper, where the same declaration is a HEIGHT basis,
   so it beat height:46px and every field collapsed to the height of its own
   text: 21px against 46px everywhere else in the app. Measured, after it was
   reported as the space inside the field being thin - which is exactly what it
   was. */
#view-citations .cit-f .ci-field, #view-localleads .cit-f .ci-field, #view-siteauditsummary .cit-f .ci-field { width:100%; flex:0 0 auto; height:46px; }

/* .ci-field input sets outline:none, so the focus ring has to be put
   back on the box that wraps it or there is no visible focus at all. */
#view-citations .cit-f .ci-field:focus-within, #view-localleads .cit-f .ci-field:focus-within, #view-siteauditsummary .cit-f .ci-field:focus-within { border-color:var(--purple); outline:2px solid var(--purple); outline-offset:1px; }

/* Local Leads only. The filter checkboxes sit side by side rather than in the
   170px grid track, because a checkbox and its sentence do not want a column
   each: they wrap as a pair and read as one group.

   Native checkboxes, deliberately. A custom indicator driven by input:checked
   plus a sibling selector does not repaint when the label is clicked rather
   than the box, which is the trap already recorded for the radio cards, and a
   filter that looks unticked while being applied is worse than a plain box. */
#view-localleads .ll-checks { flex-direction:row; flex-wrap:wrap; gap:14px; align-items:center; }
#view-localleads .ll-check { display:inline-flex; align-items:center; gap:8px; font-size:12px; color:var(--text-2); cursor:pointer; }
/* The rating row: the value group and the direction group on one line, so they
   read as the single sentence they are. Wraps rather than squeezing, because
   the .cit-grid column is only 170px at its narrowest and this cell spans the
   whole row with .cit-f--wide. */
.ll-rate { display:flex; flex-wrap:wrap; align-items:center; gap:10px; }
#view-localleads .ll-check input { width:15px; height:15px; accent-color:var(--brand-solid); cursor:pointer; flex:0 0 auto; }
/* The address under the business name. Its own line, dimmer, because it is how
   you tell two listings of the same trade apart rather than something to read
   down the column. Many rows have no address at all - the provider leaves both
   of its address fields empty on a business that drives to its customers - so
   this element is absent rather than empty on those. */
.mvx.mv-results .ll-addr { display:block; margin-top:2px; font-size:11px; color:var(--text-3); }

/* NOTE ON THE SELECTOR: .mvx.mv-results is COMPOUND, no space. The result
   container carries both classes on the SAME element (<div id="sasRes"
   class="mvx mv-results">), so the descendant form .mvx .mv-results matches
   nothing and every rule below silently did nothing. The findings rendered as
   bare divs with no card, border or padding, and no gate noticed.

   Site Audit Summary. The report is the deliverable here - it gets exported to
   PDF and sent to the business - so it is laid out to be read on paper rather
   than scrolled. Everything below is scoped to the results container, never to
   the view, because the same markup renders in the dialog and on a share link. */
/* Label above the row, not beside it. Beside it, a wrapped grid left the
   label floating against a tall empty column. */
.mvx.mv-results .sas-scorerow { margin-top:14px; }
.mvx.mv-results .sas-scorerow + .sas-scorerow { margin-top:18px; }
/* FOUR columns, because Lighthouse reports four scores and the shared
   .mvr-kpis grid is fixed at three, which wrapped the fourth onto its own
   row every time. Two on a narrow panel rather than four squeezed. */
.mvx.mv-results .sas-scorerow .mvr-kpis,
.mvx.mv-results .sas-kpis4 { grid-template-columns:repeat(4,1fr); }
@media (max-width: 860px) {
  .mvx.mv-results .sas-scorerow .mvr-kpis,
  .mvx.mv-results .sas-kpis4 { grid-template-columns:repeat(2,1fr); }
}
.mvx.mv-results .sas-dev { display:block; margin-bottom:7px; font-size:11px; font-weight:600; letter-spacing:.05em; text-transform:uppercase; color:var(--text-3); }
/* Green, amber, red, on the thresholds Google itself uses and states on the
   report, so a reader comparing the two sees the same bands. */
.mvx.mv-results .sas-good { color:var(--green-solid); }
.mvx.mv-results .sas-watch { color:var(--amber); }
.mvx.mv-results .sas-bad { color:var(--red); }
.mvx.mv-results .sas-info { color:var(--text-3); }


.mvx.mv-results .sas-findings { display:flex; flex-direction:column; gap:10px; margin-top:12px; }
.mvx.mv-results .sas-find { padding:12px 14px; border:1px solid var(--border); border-radius:var(--radius-sm); background:var(--mv-result-raise); }
/* No left accent stripe: the constitution forbids it and the severity badge
   already carries the colour. */
.mvx.mv-results .sas-find-h { display:flex; align-items:center; gap:9px; flex-wrap:wrap; }
.mvx.mv-results .sas-find-t { font-size:13.5px; font-weight:600; color:var(--text); }
/* The measured value, which is the whole point: it sits directly under the
   claim it supports so the two cannot be read apart. */
.mvx.mv-results .sas-find-e { margin-top:5px; font-size:12px; font-weight:600; color:var(--text-2); font-variant-numeric:tabular-nums; }
.mvx.mv-results .sas-find-f { margin-top:6px; font-size:12.5px; line-height:1.6; color:var(--text-2); }
.mvx.mv-results .sas-find-s { margin-top:7px; font-size:10.5px; letter-spacing:.03em; text-transform:uppercase; color:var(--text-3); }

.mvx.mv-results .sas-unchecked { display:flex; flex-direction:column; gap:7px; margin-top:10px; }
.mvx.mv-results .sas-unc { display:flex; gap:10px; flex-wrap:wrap; font-size:12px; line-height:1.55; color:var(--text-3); }
.mvx.mv-results .sas-unc b { flex:0 0 auto; min-width:180px; color:var(--text-2); font-weight:600; }

/* On paper. The exporter rasterises this element, so the findings must not be
   cut in half across a page break. */
@media print {
  .mvx.mv-results .sas-find { break-inside:avoid; }
}

/* Dropdowns, matched to the text inputs beside them.

   .ci-field input has been styled since the field existed; .ci-field select
   never was, because no tool had put one in a field until Local Leads did.
   The result was three native dropdowns in the same grid as the styled text
   boxes, each a different height with its own border drawn inside a field that
   already has one. Same values as the input rule, so the two read as one
   control set. */
#view-citations .ci-field select, #view-localleads .ci-field select, #view-siteauditsummary .ci-field select {
  flex:1; min-width:0; background:none; border:none; outline:none;
  color:var(--text); font-size:14px; font-family:"Inter",sans-serif;
  cursor:pointer; appearance:none; -webkit-appearance:none;
  /* Room for the caret drawn below, so a long option does not run under it. */
  padding:0 18px 0 0;
}
/* The caret, because appearance:none removes the native one. A background
   image rather than a pseudo-element: select cannot carry ::after. */
#view-citations .ci-field, #view-localleads .ci-field, #view-siteauditsummary .ci-field {
  position:relative;
}
#view-citations .ci-field:has(select)::after, #view-localleads .ci-field:has(select)::after, #view-siteauditsummary .ci-field:has(select)::after {
  content:""; position:absolute; right:12px; top:50%; width:8px; height:8px;
  margin-top:-5px; pointer-events:none;
  border-right:2px solid var(--text-3); border-bottom:2px solid var(--text-3);
  transform:rotate(45deg);
}
#view-citations .ci-field select option, #view-localleads .ci-field select option, #view-siteauditsummary .ci-field select option {
  background:var(--panel); color:var(--text);
}

/* The report is the PDF, so the result panel is how you get it rather than
   the report itself. Scoped .mvx.mv-results, never #view-siteauditsummary:
   the dialog MOVES this markup onto <body>, and a view-scoped rule would stop
   matching the instant it opened. */
.mvx.mv-results .sas-ready {
  display:flex; flex-direction:column; align-items:center; gap:14px;
  padding:30px 24px; margin-top:14px; text-align:center;
  /* --mvr-surface and --mvr-line are declared on .mvr, which this container
     does not carry, so they resolved to nothing and the panel painted
     transparent with its padding intact. Matched to .sas-find above, which is
     the sibling card in this same container and demonstrably paints. */
  background:var(--mv-result-raise); border:1px solid var(--border);
  border-radius:var(--radius-lg);
}
.mvx.mv-results .sas-ready-sum { font-size:15px; font-weight:650; color:var(--text); }
.mvx.mv-results .sas-ready-note {
  font-size:12.5px; line-height:1.6; color:var(--muted); max-width:46ch;
}
.mvx.mv-results .sas-dl { padding:12px 22px; font-size:14px; }

/* The Result Shell's .mvr-empty reads --mvr-surface and --mvr-line, which
   css/mvr.css declares on .mvr. These three tools render into .mvx.mv-results,
   which never carries .mvr, so both resolved to nothing and the failure panel
   shipped with no background AND no border: an invalid var() inside the
   `border` shorthand drops the whole declaration, so border-color was set and
   border-style was none. Measured in a browser, on the element itself; an
   earlier check walked up for the first painted ancestor and reported that
   instead, which is exactly how this stayed invisible.
   Pinned to the values already in scope here rather than redefining a token. */
.mvx.mv-results .mvr-empty { background:var(--mv-result-raise); border:1px solid var(--border); }
.mvx.mv-results .mvr-empty.is-error { border-color:var(--red); }

/* One PDF button, not two. The export row’s red PDF and the panel’s own
   button hand over the SAME file, and two controls for one download read as
   two different documents. The panel’s button is the action here, so the
   row’s PDF is hidden. Excel, CSV, JSON and Share stay: those are different
   files. Paired with .mv-as-siteauditsummary because the dialog moves the
   export row onto <body>, where a view-scoped rule stops matching. */
#view-siteauditsummary .ci-exports-row .tb-red,
.mv-as-siteauditsummary .ci-exports-row .tb-red { display:none !important; }

/* The button states. The report builds in milliseconds, so this is the only
   feedback slow enough to actually read. */
.mvx.mv-results .sas-dl { min-width:252px; transition:opacity .15s ease; }
.mvx.mv-results .sas-dl[disabled] { cursor:default; }
.mvx.mv-results .sas-dl.is-working { opacity:.72; }
.mvx.mv-results .sas-dl.is-done { opacity:1; }

/* Bulk audit. Named .sasb-* and left unscoped on purpose: the batch list is
   result markup, and the results dialog MOVES result markup onto <body>, so a
   #view-siteauditsummary rule would stop matching the instant it opened. */
.sasb-pickrow { display:flex; align-items:center; gap:10px; margin-bottom:10px; flex-wrap:wrap; }
.sasb-pick {
  display:inline-flex; align-items:center; gap:7px; cursor:pointer;
  padding:9px 14px; border:1px solid var(--border); border-radius:var(--radius-sm);
  background:var(--surface-2); color:var(--text); font-size:13px; font-weight:600;
}
.sasb-pick:hover { border-color:var(--brand); }
.sasb-pick input { position:absolute; width:1px; height:1px; opacity:0; pointer-events:none; }
.sasb-file { font-size:12.5px; color:var(--muted); }
.sasb-sum { margin-top:10px; font-size:12.5px; line-height:1.55; color:var(--muted); }

.mvx.mv-results .sasb-list { display:flex; flex-direction:column; gap:6px; margin-top:12px; }
.mvx.mv-results .sasb-row {
  display:grid; grid-template-columns:28px 1fr auto auto; align-items:center; gap:10px;
  padding:9px 12px; border:1px solid var(--border); border-radius:var(--radius-sm);
  background:var(--mv-result-raise); font-size:13.5px;
}
.mvx.mv-results .sasb-n { color:var(--muted); font-size:12px; font-variant-numeric:tabular-nums; }
.mvx.mv-results .sasb-site { font-weight:600; color:var(--text); overflow-wrap:anywhere; }
.mvx.mv-results .sasb-state { font-size:12.5px; color:var(--muted); white-space:nowrap; }
.mvx.mv-results .sasb-state.is-run { color:var(--brand); }
.mvx.mv-results .sasb-state.is-ok { color:var(--green-solid); }
.mvx.mv-results .sasb-state.is-bad { color:var(--red); }
.mvx.mv-results .sasb-act { min-width:46px; text-align:right; }
.mvx.mv-results .sasb-dl {
  padding:5px 11px; border:1px solid var(--border); border-radius:var(--radius-xs);
  background:var(--surface-2); color:var(--text); font-size:12px; font-weight:600; cursor:pointer;
}
.mvx.mv-results .sasb-dl:hover { border-color:var(--brand); }
.mvx.mv-results .sasb-foot { margin-top:12px; }
.mvx.mv-results .sasb-stopbtn { font-size:12.5px; padding:7px 13px; }

/* One input per website. Scrolls rather than growing without limit, because a
   hundred-row sheet would otherwise push the Run button off the screen. */
.sasb-rows { display:flex; flex-direction:column; gap:6px; max-height:252px; overflow-y:auto; }
.sasb-inrow { display:flex; align-items:center; gap:6px; }
.sasb-in {
  flex:1; min-width:0; height:40px; padding:0 12px;
  border:1px solid var(--border); border-radius:var(--radius-sm);
  background:var(--surface-2); color:var(--text);
  font-family:"Inter",sans-serif; font-size:13.5px;
}
.sasb-in:focus { outline:none; border-color:var(--brand); }
.sasb-rm {
  flex:none; width:30px; height:30px; display:inline-flex; align-items:center; justify-content:center;
  border:1px solid transparent; border-radius:var(--radius-xs);
  background:none; color:var(--muted); cursor:pointer;
}
.sasb-rm:hover { color:var(--red); border-color:var(--border); }
.sasb-add {
  margin-top:8px; display:inline-flex; align-items:center; gap:6px;
  padding:7px 12px; border:1px dashed var(--border); border-radius:var(--radius-sm);
  background:none; color:var(--text); font-size:12.5px; font-weight:600; cursor:pointer;
}
.sasb-add:hover { border-color:var(--brand); border-style:solid; }

/* Two buttons stacked, both reading "Audit this site": the app-wide
   connected-site shortcut above this tool's own Run button. The address field
   directly above already does what the shortcut does, so the shortcut is
   hidden here rather than asking anyone to tell them apart.
   Paired with .mv-as-siteauditsummary so the results-dialog ratchet does not
   rise, even though the run row is never adopted into the dialog. */
#view-siteauditsummary .ci-site-btn,
.mv-as-siteauditsummary .ci-site-btn { display:none !important; }

/* The half that is not in use. */
.sasb-off { opacity:.45; }
.sasb-off .ci-field { background:var(--surface-2); }
.sasb-in:disabled, .sasb-off input { cursor:not-allowed; }

/* The batch row's report link, and the screenshots on the public share page.
   Scoped .mvx.mv-results like the rest of this result: the share page links
   this stylesheet, so the public report picks the same rules up. */
.mvx.mv-results .sasb-row { grid-template-columns:28px 1fr auto auto auto; }
.mvx.mv-results .sasb-link { min-width:40px; text-align:right; }
.mvx.mv-results .sasb-linka {
  font-size:12px; font-weight:600; color:var(--brand); text-decoration:none;
  padding:5px 9px; border:1px solid var(--border); border-radius:var(--radius-xs);
}
.mvx.mv-results .sasb-linka:hover { border-color:var(--brand); }

/* ---- the public Site Audit report -----------------------------------------
   The shared link is the same document as the PDF, so it is laid out like one:
   a title with the date, the opening paragraph, a numbered list that carries
   the score rings and the screenshots inside item 6, then the closing note.

   The rings are .psi-gauge from css/psi.css, which the share page links.
   Nothing about them is restyled here; this only places them. */
.mvx.mv-results.sas-pub { color: var(--text); }
.sas-pub .sas-pub-top {
  display: flex; align-items: baseline; justify-content: space-between;
  gap: 16px; flex-wrap: wrap; margin-bottom: 10px;
}
.sas-pub .sas-pub-t { margin: 0; font-size: 26px; font-weight: 700; color: var(--text); letter-spacing: -0.01em; }
.sas-pub .sas-pub-date { font-size: 12.5px; color: var(--text-3); white-space: nowrap; }
.sas-pub .sas-pub-intro {
  margin: 0 0 18px; max-width: 70ch; font-size: 14px; line-height: 1.6; color: var(--text-2);
}

/* The numbering is the document's own: the screenshot block is item 6 and the
   findings carry on from it, exactly as the PDF numbers them. */
.sas-pub .sas-pub-list { margin: 0; padding-left: 26px; display: flex; flex-direction: column; gap: 9px; }
.sas-pub .sas-pub-list > li { font-size: 14px; line-height: 1.55; color: var(--text); }

/* Rings on their own row, then the screenshot on its own line under them, with
   the caption that names the device directly beneath the picture. The way the
   PDF sets it out, and this page is meant to be the same document.

   It used to put the rings left and the screenshot beside them, with the
   caption at the left edge below. Two device blocks then read as two unlabelled
   pictures down the right side and two labels down the left, and a reader could
   not tell which screenshot was the phone. */
.sas-pub .sas-pub-dev {
  display: flex; flex-direction: column; align-items: flex-start; gap: 12px; margin: 12px 0 2px;
}
.sas-pub .sas-pub-gauges { display: flex; gap: 2px; flex-wrap: wrap; }
/* The four labels are wider than their rings, so without a floor under each
   cell "Performance" and "Accessibility" touch and read as one word. */
.sas-pub .psi-gauge { padding: 8px 6px; min-width: 100px; }
/* The ring size, which js/mv-psi.js sets inline per call. Fixed here, because
   this page always draws them at one size and dashboard.html is inside the
   design ratchet. */
.sas-pub .psi-gauge-inner { --sz: 64px; }
/* A cap is still needed even on its own line: a phone screenshot is about twice
   as tall as it is wide, and left to its natural height it pushes the findings
   off the first screen. Generous enough to be worth looking at now that nothing
   sits beside it. */
.sas-pub .sas-pub-shot { flex: 0 0 auto; max-width: 100%; }
.sas-pub .sas-pub-shot img {
  display: block; width: auto; max-width: 100%; height: auto; max-height: 190px;
  object-fit: contain; object-position: top;
  border: 1px solid var(--border); border-radius: var(--radius-sm); background: var(--surface);
}
.sas-pub .sas-pub-cap { font-size: 12px; color: var(--text-3); margin-bottom: 14px; }
.sas-pub .sas-pub-dev-miss {
  margin: 10px 0 14px; font-size: 13px; line-height: 1.55; color: var(--text-2);
}

.sas-pub .sas-pub-unc { margin-top: 22px; }
.sas-pub .sas-pub-unc h2 { margin: 0 0 8px; font-size: 15px; font-weight: 700; color: var(--text); }
.sas-pub .sas-pub-unc ul { margin: 0; padding-left: 20px; display: flex; flex-direction: column; gap: 4px; }
.sas-pub .sas-pub-unc li { font-size: 13px; line-height: 1.5; color: var(--text-2); }

.sas-pub .sas-pub-note {
  margin: 22px 0 0; max-width: 70ch; font-size: 13px; line-height: 1.6; color: var(--text-2);
}
.sas-pub .sas-pub-note b { color: var(--text); }

/* A phone opens this as often as a desktop does, and the rings must not force
   the page sideways. */
/* The block stacks at every width now, so this is only about the ring row,
   which must not force the page sideways on a phone. */
@media (max-width: 560px) {
  .sas-pub .sas-pub-gauges { gap: 0; }
  .sas-pub .psi-gauge { padding: 8px 6px; }
}

/* Printing the shared page should give back something close to the PDF. */
@media print {
  .sas-pub .sas-pub-dev { break-inside: avoid; }
  .sas-pub .sas-pub-list > li { break-inside: avoid; }
}

/* ---- Local Leads: past searches --------------------------------------------
   Under the result, above the explainer. Deliberately NOT .mvr-* components:
   those read their surface, border and muted colours from variables declared
   on a .mvr wrapper, and this panel sits outside #llRes, so borrowing them
   would paint an invisible heading. Everything here comes from tokens.

   No #view- prefix either: the results dialog moves a view's markup onto
   <body>, where a rule written as `#view-x .thing` stops applying, and
   tests/results-dialog-scope.mjs counts every one of those. The `llh-`
   names are unique on their own, so the prefix only bought debt. */
.llh { margin-top: 26px; }
.llh-head { margin-bottom: 10px; }
.llh-title {
  margin: 0; font-size: 15px; font-weight: 700; color: var(--text);
}
.llh-sub {
  margin: 4px 0 0; font-size: 12.5px; line-height: 1.55; color: var(--text-3); max-width: 70ch;
}
.llh-list { display: flex; flex-direction: column; gap: 6px; }

/* A button, not a div with a click handler, so the keyboard reaches every row
   without a tabindex and a roving-focus implementation to keep correct. */
.llh-row {
  display: grid; grid-template-columns: 1fr auto auto; align-items: center; gap: 14px;
  width: 100%; text-align: left; padding: 10px 14px;
  border: 1px solid var(--border); border-radius: var(--radius-sm);
  background: var(--mv-result-raise); color: var(--text);
  font: inherit; font-size: 13px; cursor: pointer;
  transition: border-color .15s, background .15s;
}
.llh-row:hover { border-color: var(--purple); }
.llh-row:focus-visible { outline: 2px solid var(--purple); outline-offset: 1px; }
/* The row whose result is on screen. A left stripe is what rule 5 of the
   design constitution forbids, so the whole border carries it instead. */
.llh-row.is-open { border-color: var(--purple); }
.llh-row.is-loading { opacity: .55; pointer-events: none; }

.llh-q {
  font-weight: 600; overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
.llh-when { font-size: 12px; color: var(--text-3); white-space: nowrap; }
/* Tabular figures so the credit column lines up down the list. */
.llh-cr {
  font-size: 12px; color: var(--text-2); font-variant-numeric: tabular-nums;
  min-width: 2.5ch; text-align: right;
}

.llh-more {
  margin-top: 10px; padding: 8px 14px;
  border: 1px solid var(--border-strong); border-radius: var(--radius-sm);
  background: transparent; color: var(--text-2);
  font: inherit; font-size: 12.5px; font-weight: 600; cursor: pointer;
}
.llh-more:hover { border-color: var(--purple); color: var(--text); }

/* On a phone the credit figure is the first thing worth dropping: the search
   and when it ran are what somebody scans for. */
@media (max-width: 560px) {
  .llh-row { grid-template-columns: 1fr auto; gap: 10px; }
  .llh-cr { display: none; }
}
