/*
 * Mass Tort Intake — styled to match masstortintakecenter.com.
 *
 * Every value here was read from the live site's computed styles, not eyeballed
 * from a screenshot:
 *
 *   brand maroon   rgb(141, 2, 31)  #8d021f   header rule, hero band, buttons
 *   body text      rgb(51, 51, 51)  #333333
 *   headings       Open Sans 700
 *   body font      the system stack — which is what the main site actually uses
 *
 * The logo and the font are SELF-HOSTED in public/. Loading them from the main
 * domain would put a third-party request on the critical path of a page people
 * arrive at from an ad, and would break the moment the strict CSP or the main
 * site's media library changed. One copy here, no external requests at all.
 */

/* Open Sans, latin subset, variable weight — one 43KB file for 400 through 700. */
@font-face {
  font-family: 'Open Sans';
  font-style: normal;
  font-weight: 300 800;
  font-display: swap;
  src: url('/fonts/open-sans.woff2') format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA,
    U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193,
    U+2212, U+2215, U+FEFF, U+FFFD;
}

:root {
  --brand: #8d021f;
  --brand-dark: #6d0117;
  --brand-tint: #f7ecee;
  --ink: #333333;
  --ink-soft: #54595f;
  --line: #d9dde2;
  --bg: #ffffff;
  --bg-soft: #f4f5f7;
  --error: #b3261e;
  --focus: #8d021f;
  --radius: 6px;
  --heading: 'Open Sans', -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;
  --body: -apple-system, system-ui, 'Segoe UI', Roboto, 'Helvetica Neue', Arial,
    'Noto Sans', sans-serif;
}

*, *::before, *::after { box-sizing: border-box; }

/*
 * `hidden` must actually hide.
 *
 * The attribute sets `display: none` through the user-agent stylesheet, which
 * ANY author `display` rule overrides. `.bullets` is `display: flex`, so after
 * a successful submission the reassurance points stayed on screen next to the
 * thank-you message. Caught by looking at the page; no test would have.
 */
[hidden] { display: none !important; }

html { -webkit-text-size-adjust: 100%; }

body {
  margin: 0;
  background: var(--bg);
  color: var(--ink);
  font: 16px/1.6 var(--body);
}

h1, h2, h3, .site-phone, .submit, .eyebrow {
  font-family: var(--heading);
}

/* ── Site header — logo left, phone right, matching the main site ────────── */

.site-header {
  background: var(--bg);
  border-bottom: 4px solid var(--brand);
}

.site-header-inner {
  max-width: 62rem;
  margin: 0 auto;
  padding: .75rem 1rem;
  display: flex;
  align-items: center;
  justify-content: space-between;
  /*
   * Wrapping is not decoration here. A 200px logo, three icons and a phone
   * number do not fit across 375px, and without this the header pushed the
   * whole document wider than the screen — every section then sat in a
   * 505px-wide canvas with a white gutter down the side of the phone.
   */
  flex-wrap: wrap;
  gap: .5rem 1rem;
}

.site-logo { display: block; }
/* 200px, against the main site's 249 — the same lockup, a little smaller,
   because this page has no navigation to balance it against. */
.site-logo img { display: block; width: 150px; height: auto; }

/* The main site carries these in its header; without them this page was
   recognisably a different site with the same logo on it. */
/* Hidden on a phone, where the header has room for the logo and the phone
   number and nothing else. They are not why anyone is on this page. */
.site-social { display: none; gap: .4rem; margin: 0 auto 0 .5rem; padding: 0; list-style: none; }

@media (min-width: 30rem) {
  .site-social { display: flex; }
}

@media (min-width: 62rem) {
  .site-logo img { width: 200px; }
}
.site-social a {
  display: grid;
  place-items: center;
  width: 1.85rem;
  height: 1.85rem;
  border-radius: 3px;
  background: var(--brand);
  color: #fff;
}
.site-social a:hover { background: var(--brand-dark); }

.site-phone {
  color: var(--brand);
  font-weight: 700;
  font-size: .95rem;
  text-transform: uppercase;
  text-decoration: none;
  white-space: nowrap;
}
.site-phone:hover { text-decoration: underline; }

/* ── Hero band — the maroon block the main site opens with ───────────────── */

.hero {
  position: relative;
  isolation: isolate;
  background: var(--brand);
  color: #fff;
  padding: 1.75rem 1rem 2rem;
}

/* ── The hero's photograph ───────────────────────────────────────────────────
 *
 * Visible. That is the whole requirement, and the first attempt failed it: a
 * scrim at 96% opacity across the entire band left between two and twelve per
 * cent of the picture showing, which is not a dark photograph, it is a maroon
 * rectangle. Contrast for the text was excellent and the image had been
 * painted out — solving the wrong problem perfectly.
 *
 * The darkness now goes only where the words are. The left of the band is
 * covered enough to read white text against; from about the middle it falls
 * away and the photograph is simply the photograph. The form's own white card
 * sits over the right-hand side, so nothing there needs protecting.
 */
.hero-media {
  position: absolute;
  inset: 0;
  z-index: -1;
  overflow: hidden;
}

.hero-media img {
  width: 100%;
  height: 100%;
  object-fit: cover;
  /* Barely touched — enough to calm a saturated stock photograph, not enough
   * to make anybody wonder whether the image loaded. */
  filter: saturate(.85) brightness(.88);
}

.hero-media::after {
  content: "";
  position: absolute;
  inset: 0;
  /*
   * Measured, not guessed. Against the worst case — a blown-out white patch of
   * photograph — white text is 15.3:1 at the left edge and 9.8:1 where the
   * headline sits, both past AAA. By 60% it is deliberately too light for text
   * and there is none there.
   */
  background: linear-gradient(100deg,
    rgba(48, 0, 11, .90) 0%,
    rgba(72, 1, 16, .78) 38%,
    rgba(100, 2, 23, .45) 60%,
    rgba(120, 2, 27, .22) 100%);
}

/*
 * On a phone there is no second column: the copy and the form sit over the
 * whole width, so the picture needs covering all the way across or the form
 * lands on top of a photograph. It stays visible at the top, above the copy.
 */
@media (max-width: 61.9375rem) {
  .hero-media::after {
    background: linear-gradient(178deg,
      rgba(60, 0, 14, .28) 0%,
      rgba(72, 1, 16, .72) 26%,
      rgba(90, 1, 20, .93) 46%,
      rgba(107, 1, 24, .97) 100%);
  }
}

/*
 * One column on a phone, two on anything wider.
 *
 * Mobile stacks, and deliberately so: it is where nearly all of this traffic
 * lands. On desktop the form sits beside the copy and is visible without
 * scrolling, which is the whole job of a page people reach from an ad.
 */
.hero-grid {
  position: relative;
  max-width: 68rem;
  margin: 0 auto;
  display: grid;
  gap: 1.5rem;
}

.hero-copy { max-width: 34rem; }

@media (min-width: 62rem) {
  .hero {
    padding: 4rem 1.5rem 4.5rem;
  }
  .hero-grid {
    grid-template-columns: 1fr minmax(24rem, 27rem);
    column-gap: 4rem;
    /*
     * Top-aligned, now that the left column holds copy rather than copy plus a
     * picture stretched to meet the form. The form is taller; that is normal
     * and reads as normal, where a photograph stretched to match it did not.
     */
    align-items: start;
  }
  /* 40px at weight 500 — read off the main site's "Welcome to Mass Tort
     Intake Center", so the two pages open in the same voice. */
  .hero h1 { font-size: 2.5rem; font-weight: 500; line-height: 1.2; letter-spacing: -.01em; }
  .hero .subhead { font-size: 1.125rem; max-width: 30rem; }
  /* On its own column the card needs no negative pull. */
  .hero-form form { margin-top: 0; box-shadow: 0 18px 40px rgba(0, 0, 0, .28); }
}

/* ── What happens next ───────────────────────────────────────────────────── */

/*
 * On a phone these sit BELOW the form, which is why they are a sibling of it in
 * the markup rather than part of the copy block.
 *
 * Nearly all of this traffic is mobile, and three explanatory steps between the
 * headline and the first input push the form most of a screen further down. The
 * form comes first on a phone; the steps are there for whoever scrolls past it.
 */
.story-steps {
  list-style: none;
  margin: 0;
  padding: 0;
  counter-reset: step;
  display: grid;
  gap: 1.25rem;
}

@media (min-width: 48rem) {
  .story-steps { grid-template-columns: repeat(3, 1fr); gap: 2rem; }
}

.story-steps li {
  counter-increment: step;
  display: grid;
  grid-template-columns: 1.75rem 1fr;
  gap: .1rem .75rem;
  align-items: baseline;
}

.story-steps li::before {
  content: counter(step);
  grid-row: span 2;
  align-self: start;
  width: 1.75rem;
  height: 1.75rem;
  border-radius: 50%;
  border: 1px solid var(--brand);
  color: var(--brand);
  display: grid;
  place-items: center;
  font-size: .8125rem;
  font-weight: 700;
}

/*
 * A full-width line across the foot of the maroon band, outside the two-column
 * grid on purpose.
 *
 * Inside it, this was a third grid row — and because the form spans every row,
 * a grid shares the form's surplus height across all of them, so a two-line
 * disclaimer sat in a 220px row with 160px of empty maroon under it. Out here
 * it hugs its own text and the photograph above gets the whole surplus.
 */
.hero-note {
  max-width: 68rem;
  margin: 1.75rem auto 0;
  font-size: .8125rem;
  line-height: 1.55;
  color: #e6b9c1;
  border-top: 1px solid rgba(255, 255, 255, .22);
  padding-top: .9rem;
}

.story-steps b { font-size: .9375rem; font-weight: 700; color: var(--ink); }
.story-steps span { font-size: .875rem; color: var(--ink-soft); line-height: 1.45; }

/* Talking to a person is a real option for the people who want it, and saying
   so costs one line. */
.hero-call { margin: 1.25rem 0 0; font-size: .9375rem; color: #f0c9d0; }
.hero-call a { color: #fff; font-weight: 700; text-decoration: none; border-bottom: 2px solid rgba(255,255,255,.45); }
.hero-call a:hover { border-bottom-color: #fff; }

.eyebrow {
  margin: 0 0 .4rem;
  font-size: .75rem;
  font-weight: 700;
  letter-spacing: .08em;
  text-transform: uppercase;
  color: #f0c9d0;
}

h1 {
  margin: 0 0 .6rem;
  font-size: 1.65rem;
  line-height: 1.25;
  font-weight: 700;
}

.subhead {
  margin: 0;
  font-size: 1rem;
  color: #f4e3e6;
}

/* ── Form ────────────────────────────────────────────────────────────────── */

/*
 * 36rem, not 34rem. The hero's inner column is 34rem inside 1rem of padding, so
 * a 34rem wrap put the form card's edge exactly 1rem inside the headline above
 * it. Adding the padding to the max-width makes the two share a left edge.
 */
.wrap {
  max-width: 36rem;
  margin: 0 auto;
  padding: 1.25rem 1rem 2.5rem;
}

/*
 * The negative margin below is for the CLAIMANT HERO, where the form card is
 * meant to tuck up into the maroon band above it. Every other page that uses a
 * plain <form> inherited it — including the portal's sign-in, which is the
 * first screen a law firm ever sees, where the card slid up over its own
 * heading and cut the words in half. It had been doing that since the portal
 * was built; no test looks at a rendered page.
 */
main.legal form,
main.page form {
  margin-top: 0;
}

/*
 * Links on the portal's own pages. Scoped to `.legal` and NOT set globally:
 * the claimant landing pages are laid out deliberately and a site-wide link
 * colour is not a change to make on the way past something else.
 */
/*
 * The signed-in surfaces: the buyer's portal and the publisher's page.
 *
 * `.portal-stats`, `.stat` and `.linkish` were used by the portal and defined
 * NOWHERE — so the buyer's dashboard has been rendering its headline figures as
 * a run-on list ("48accepted") since it was built, and the sign-out control as
 * a default grey button. The admin has its own copy of these rules in its
 * inline stylesheet, which is why nobody noticed: the two surfaces look
 * identical in the code and only one of them was styled.
 */
.portal-stats {
  display: flex;
  flex-wrap: wrap;
  gap: .75rem;
  margin: 0 0 1.25rem;
}
.portal-stats .stat {
  display: flex;
  flex-direction: column;
  gap: .15rem;
  min-width: 7.5rem;
  padding: .85rem 1rem;
  background: var(--bg);
  border: 1px solid var(--line);
  border-radius: var(--radius);
  font-size: .8125rem;
  color: var(--muted, #5a6472);
}
.portal-stats .stat b {
  font-size: 1.5rem;
  line-height: 1.1;
  font-weight: 700;
  color: inherit;
  font-variant-numeric: tabular-nums;
}

/* A button that is really a link — "sign out" beside a heading. */
.linkish {
  background: none;
  border: 0;
  padding: 0;
  font: inherit;
  font-size: .875rem;
  color: inherit;
  text-decoration: underline;
  cursor: pointer;
}

main.legal a {
  color: var(--brand);
  text-decoration-thickness: 1px;
  text-underline-offset: 2px;
}
main.legal a:hover { text-decoration-thickness: 2px; }

form {
  background: var(--bg);
  /* The card now sits INSIDE the maroon band, which sets `color: #fff`. Without
     restating it here the whole form inherits white text on a white card and
     every label disappears. Caught on screen; no test would have seen it. */
  color: var(--ink);
  border: 1px solid var(--line);
  border-radius: var(--radius);
  padding: 1.25rem;
  margin-top: -1.25rem;
  position: relative;
  box-shadow: 0 2px 10px rgba(0, 0, 0, .07);
}

.row { display: grid; gap: 0; }

@media (min-width: 30rem) {
  .row { grid-template-columns: 1fr 1fr; gap: 0 .875rem; }
  h1 { font-size: 2rem; }
  .hero { padding: 2.5rem 1rem 3rem; }
  .site-logo img { width: 172px; }
  .site-phone { font-size: 1.05rem; }
}

.field { margin-bottom: 1rem; }

label {
  display: block;
  margin-bottom: .3rem;
  font-size: .9375rem;
  font-weight: 600;
}

.req { color: var(--brand); }

/* `password` was missing from this list, so every password field on the site —
   the portal sign-in, and now the reset pages — rendered at the browser's
   default width beside full-width fields above it. A visual bug that only
   shows on the two screens nobody loads while building a claimant form. */
input[type="text"], input[type="tel"], input[type="email"], input[type="password"],
select, textarea {
  width: 100%;
  padding: .7rem .75rem;
  border: 1px solid var(--line);
  border-radius: var(--radius);
  background: var(--bg);
  color: var(--ink);
  /* 16px minimum: anything smaller makes iOS Safari zoom on focus, which
     visibly jerks the page and loses people mid-form. */
  font-size: 1rem;
  font-family: inherit;
}

input:focus, select:focus, textarea:focus { border-color: var(--brand); }

textarea { resize: vertical; min-height: 5.5rem; }

select {
  appearance: none;
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='12' height='8'%3E%3Cpath fill='%2354595f' d='M1 1l5 5 5-5'/%3E%3C/svg%3E");
  background-repeat: no-repeat;
  background-position: right .8rem center;
  padding-right: 2.2rem;
}

/* The focus ring is defined once, near the end of this file, in two tones so
 * it is visible on both the white page and the maroon band. It used to be
 * `3px solid var(--focus)` — the brand maroon, on a maroon hero: 1.00:1. */

input[aria-invalid="true"], select[aria-invalid="true"] { border-color: var(--error); }

.field-error, .form-error {
  margin: .3rem 0 0;
  color: var(--error);
  font-size: .875rem;
}
.field-error:empty, .form-error:empty { display: none; }

/* ── Honeypot ─────────────────────────────────────────────────────────────
   Off-screen rather than display:none — some bots skip hidden fields, and a
   field that is merely positioned away is still filled by the naive ones. */
.hp { position: absolute; left: -9999px; width: 1px; height: 1px; overflow: hidden; }

.locked-tort {
  margin: 0;
  padding: .7rem .75rem;
  background: var(--brand-tint);
  border: 1px solid var(--line);
  border-left: 3px solid var(--brand);
  border-radius: var(--radius);
  font-weight: 600;
}
.locked-tort-label { color: var(--ink-soft); font-weight: 400; }

/* ── Consent ──────────────────────────────────────────────────────────────── */

.consent { margin: 1.25rem 0 1rem; padding-top: 1rem; border-top: 1px solid var(--line); }

.consent-check {
  display: flex;
  gap: .625rem;
  align-items: flex-start;
  font-weight: 600;
  cursor: pointer;
}

.consent-check input {
  /* A 16px checkbox is a miss target on a phone. */
  width: 1.375rem;
  height: 1.375rem;
  margin: .05rem 0 0;
  flex: 0 0 auto;
  accent-color: var(--brand);
}

.consent-text { margin: .75rem 0 0; color: var(--ink-soft); font-size: .75rem; line-height: 1.5; }

.submit {
  width: 100%;
  padding: .95rem 1rem;
  border: 0;
  border-radius: var(--radius);
  background: var(--brand);
  color: #fff;
  font-size: 1.0625rem;
  font-weight: 700;
  cursor: pointer;
}
.submit:hover { background: var(--brand-dark); }
.submit[disabled] { opacity: .6; cursor: default; }

.bullets {
  display: flex;
  flex-wrap: wrap;
  gap: .55rem 1.5rem;
  margin: 1.5rem 0 0;
  padding: 0;
  list-style: none;
  color: #f4e3e6;
  font-size: .9375rem;
}
.bullets li { display: flex; align-items: center; gap: .45rem; }
/* On the maroon band the tick has to be light, not brand-coloured. */
.bullets li::before { content: "✓"; color: #fff; font-weight: 700; opacity: .85; }

.thanks {
  background: var(--bg);
  color: var(--ink);
  border: 1px solid var(--line);
  border-top: 4px solid var(--brand);
  border-radius: var(--radius);
  padding: 1.75rem 1.25rem;
  text-align: center;
}
.thanks h2 { margin: 0 0 .5rem; font-size: 1.35rem; }
.thanks p { margin: 0; color: var(--ink-soft); }

/* ── Footer — the main site's legal disclosure, same wording ─────────────── */

.site-footer {
  background: var(--bg-soft);
  border-top: 1px solid var(--line);
  color: var(--ink-soft);
  font-size: .72rem;
  line-height: 1.6;
}

.site-footer-inner { max-width: 68rem; margin: 0 auto; padding: 2rem 1rem 2.5rem; }

/*
 * The required disclosures are long, and on a wide screen a single 42rem column
 * of 11px grey text left a third of the page empty below it and looked like the
 * page had run out. Two columns use the width the header and hero already use,
 * and halve the height of the wall.
 *
 * `columns` and not a grid, deliberately: the number of paragraphs is content,
 * not layout, and the browser balances whatever is there.
 */
@media (min-width: 62rem) {
  .disclosure-body { columns: 2; column-gap: 3rem; }
  .disclosure-body p { break-inside: avoid; }
}

.site-footer h2 {
  margin: 0 0 .5rem;
  font-size: .72rem;
  font-weight: 700;
  letter-spacing: .06em;
  text-transform: uppercase;
  color: var(--ink);
}

.site-footer p { margin: 0 0 .6rem; }
.site-footer a { color: var(--ink-soft); }
.footer-links { margin-top: .9rem; }

/* ── The photo-led block, the shape the main site is built out of ────────── */

.story {
  background: var(--bg-soft);
  border-top: 1px solid var(--line);
  padding: 2.5rem 1rem;
}

.story-grid {
  max-width: 68rem;
  margin: 0 auto;
  display: grid;
  gap: 1.5rem;
  align-items: center;
}

@media (min-width: 62rem) {
  .story { padding: 3.5rem 1.5rem; }
}

.story-copy { max-width: 46rem; }
.story-cta { margin: 0; }

/* Read from the live site: Open Sans 700, 28px, uppercase, brand maroon. */
.story-copy h2 {
  margin: 0 0 .75rem;
  font-size: 1.75rem;
  line-height: 1.3;
  font-weight: 700;
  text-transform: uppercase;
  color: var(--brand);
}

.story-copy p { margin: 0 0 .9rem; color: var(--ink); }

/* The main site's button, to the pixel: 20px/700, 12x24 padding, 3px radius. */
.btn-brand {
  display: inline-block;
  margin-top: .4rem;
  padding: 12px 24px;
  background: var(--brand);
  color: #fff;
  font-family: var(--heading);
  font-size: 1.05rem;
  font-weight: 700;
  text-transform: uppercase;
  text-decoration: none;
  border-radius: 3px;
}
.btn-brand:hover { background: var(--brand-dark); }

/* ── Pre-qualification questions ─────────────────────────────────────────── */

.tort-questions {
  margin: 0 0 1rem;
  padding: 1rem 1rem .25rem;
  border: 1px solid var(--line);
  border-left: 3px solid var(--brand);
  border-radius: var(--radius);
  background: var(--brand-tint);
}

.q-label { display: block; margin-bottom: .35rem; font-weight: 600; }
.q-help { margin: 0 0 .5rem; color: var(--ink-soft); font-size: .8125rem; }

/*
 * Who is asking, sitting directly above the form.
 *
 * Quiet but legible: it is a reassurance, not a warning, and styling it like a
 * warning would make a straightforward claim page look like it has something to
 * apologise for. Tokens only, so it follows the page into dark mode — the bug
 * that made the questions block invisible came from a hard-coded surface.
 */
.form-identity {
  margin: 0 0 1rem;
  padding: .7rem .9rem;
  background: var(--bg-soft);
  border-left: 3px solid var(--brand);
  border-radius: var(--radius);
  color: var(--ink-soft);
  font-size: .8125rem;
  line-height: 1.5;
}

.form-identity strong { color: var(--ink); }

.q-options { display: flex; flex-wrap: wrap; gap: .5rem; }

.q-option {
  display: flex;
  align-items: center;
  gap: .5rem;
  margin: 0;
  padding: .6rem .9rem;
  background: var(--bg);
  border: 1px solid var(--line);
  border-radius: var(--radius);
  font-weight: 500;
  cursor: pointer;
}

/* A whole tapped tile, not a 16px circle. */
.q-option input { width: 1.2rem; height: 1.2rem; accent-color: var(--brand); }
.q-option:has(input:checked) { border-color: var(--brand); background: var(--bg); box-shadow: inset 0 0 0 1px var(--brand); }

/* ── Legal pages and the 404 ──────────────────────────────────────────────────
 *
 * A privacy policy is read by somebody who is already uneasy — they have just
 * been asked for a phone number and a medical history. Long measure, generous
 * leading, and nothing clever: the job is to be legible, not to be designed.
 */
.legal {
  max-width: 44rem;
  margin: 0 auto;
  padding: 3rem 1.25rem 4rem;
}

.legal h1 {
  font-size: clamp(1.75rem, 4vw, 2.375rem);
  line-height: 1.2;
  margin: 0 0 .5rem;
}

.legal-updated {
  color: var(--ink-soft);
  font-size: .875rem;
  margin: 0 0 1.5rem;
}

.legal-intro {
  font-size: 1.0625rem;
  line-height: 1.65;
  padding-bottom: 1.5rem;
  border-bottom: 1px solid var(--line);
  margin: 0 0 .5rem;
}

.legal-section { margin-top: 2.25rem; }

.legal-section h2 {
  font-size: 1.1875rem;
  line-height: 1.3;
  margin: 0 0 .75rem;
  color: var(--brand);
}

/* The measure is what makes a policy readable, so it is set on the paragraph
 * rather than on a wrapper somebody might later drop. */
.legal-section p,
.legal-intro {
  max-width: 40rem;
}

.legal-section p {
  line-height: 1.7;
  margin: 0 0 1rem;
}

.legal .button {
  display: inline-block;
  background: var(--brand);
  color: #fff;
  font-family: var(--heading);
  font-weight: 700;
  text-decoration: none;
  padding: .875rem 1.5rem;
  border-radius: var(--radius);
  margin: .5rem 0 1.5rem;
}

.legal .button:hover { background: var(--brand-dark); }

/* ── Navigation ───────────────────────────────────────────────────────────────
 *
 * Plain lists, no JavaScript. It works before the script loads and if it never
 * loads, and it is keyboard-operable without anyone writing key handlers. On a
 * narrow screen the nav wraps under the logo rather than collapsing behind a
 * button: five items fit, and a disclosure widget is a thing to get wrong for
 * no gain.
 */
.site-nav ul {
  list-style: none;
  margin: 0;
  padding: 0;
  display: flex;
  flex-wrap: wrap;
  gap: .25rem 1.25rem;
}

.site-nav a {
  color: var(--ink);
  text-decoration: none;
  font-family: var(--heading);
  font-weight: 600;
  font-size: .9375rem;
  /* Vertical padding, not margin: it makes the tap target 44px tall, which is
   * the minimum a finger can hit reliably and what WCAG 2.1 asks for. */
  display: inline-block;
  padding: .625rem 0;
  border-bottom: 2px solid transparent;
}

.site-nav a:hover { color: var(--brand); border-bottom-color: var(--brand); }

/* The current page is marked with a colour AND a rule, because colour alone
 * is not a distinction for everyone who has to see it. */
.site-nav a[aria-current="page"] {
  color: var(--brand);
  border-bottom-color: var(--brand);
}

/*
 * Keyboard users land here first. Off-screen until focused, then visible —
 * without it, reaching the form on a page with a full nav means tabbing through
 * every link on every page.
 */
.skip-link {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 100;
  background: var(--brand);
  color: #fff;
  padding: .75rem 1.25rem;
  font-family: var(--heading);
  font-weight: 700;
  text-decoration: none;
}

.skip-link:focus {
  left: 0;
}

/* ── Content pages ───────────────────────────────────────────────────────── */

.page { padding: 2.5rem 1.25rem 3rem; }

.page-inner { max-width: 52rem; margin: 0 auto; }

.page h1 {
  font-size: clamp(1.875rem, 4.5vw, 2.5rem);
  line-height: 1.15;
  margin: 0 0 .75rem;
}

.page-intro {
  font-size: 1.125rem;
  line-height: 1.6;
  color: var(--ink-soft);
  max-width: 40rem;
  margin: 0 0 2rem;
}

.page-section { margin-top: 2.5rem; }

.page-section h2 {
  font-size: 1.375rem;
  line-height: 1.25;
  margin: 0 0 .875rem;
}

.page-section p { line-height: 1.7; max-width: 40rem; margin: 0 0 1rem; }

.page-list { line-height: 1.7; max-width: 40rem; padding-left: 1.25rem; }
.page-list li { margin-bottom: .5rem; }

/* Numbered steps. The counter is drawn rather than left to the list marker so
 * it can be a filled circle at a readable size. */
.steps { list-style: none; counter-reset: step; margin: 0; padding: 0; }

.steps li {
  counter-increment: step;
  position: relative;
  padding-left: 3.25rem;
  margin-bottom: 1.75rem;
}

.steps li::before {
  content: counter(step);
  position: absolute;
  left: 0;
  top: 0;
  width: 2.25rem;
  height: 2.25rem;
  border-radius: 50%;
  background: var(--brand);
  color: #fff;
  font-family: var(--heading);
  font-weight: 700;
  display: flex;
  align-items: center;
  justify-content: center;
}

.steps h3 { font-size: 1.0625rem; margin: .25rem 0 .375rem; }
.steps p { margin: 0; line-height: 1.65; }

/* ── The claim grid ─────────────────────────────────────────────────────────
 *
 * `auto-fill` with a minimum rather than fixed columns: it reflows from one
 * column on a phone to four on a desktop with no breakpoints to maintain, and
 * nothing is ever narrower than 15rem.
 */
.claim-grid {
  list-style: none;
  margin: 0;
  padding: 0;
  display: grid;
  grid-template-columns: repeat(auto-fill, minmax(15rem, 1fr));
  gap: 1rem;
}

.claim-card {
  border: 1px solid var(--line);
  border-radius: var(--radius);
  padding: 1.125rem 1.25rem;
  background: var(--bg);
}

.claim-card h3 { font-size: 1.0625rem; margin: 0 0 .5rem; }

.claim-card h3 a {
  color: var(--brand);
  text-decoration: none;
}

.claim-card h3 a:hover { text-decoration: underline; }

/* The whole card is the target, not just the words. `::after` over the card
 * means a finger anywhere on it works, while the link text stays the thing a
 * screen reader announces. */
.claim-card { position: relative; }

.claim-card h3 a::after {
  content: "";
  position: absolute;
  inset: 0;
}

.claim-card p { margin: 0; font-size: .9375rem; line-height: 1.55; color: var(--ink-soft); }

.claim-card:hover { border-color: var(--brand); }

/* ── Questions ──────────────────────────────────────────────────────────────
 *
 * <details>, not a JavaScript accordion: it opens with the keyboard, it is
 * announced correctly, it is searchable by the browser's own find, and it works
 * with the script blocked.
 */
.faq-item {
  border-bottom: 1px solid var(--line);
}

.faq-item summary {
  font-family: var(--heading);
  font-weight: 600;
  font-size: 1.0625rem;
  padding: 1rem 2rem 1rem 0;
  cursor: pointer;
  position: relative;
  list-style: none;
}

.faq-item summary::-webkit-details-marker { display: none; }

.faq-item summary::after {
  content: "+";
  position: absolute;
  right: .25rem;
  top: 50%;
  transform: translateY(-50%);
  font-size: 1.5rem;
  line-height: 1;
  color: var(--brand);
}

.faq-item[open] summary::after { content: "\2212"; }

.faq-item p {
  margin: 0 0 1.125rem;
  line-height: 1.7;
  max-width: 42rem;
}

/* ── The call to action above the footer ───────────────────────────────────── */

.cta-band {
  background: var(--brand-tint);
  border-top: 1px solid var(--line);
  padding: 3rem 1.25rem;
  text-align: center;
}

.cta-inner { max-width: 42rem; margin: 0 auto; }

.cta-band h2 { font-size: clamp(1.375rem, 3.5vw, 1.75rem); margin: 0 0 .625rem; }
.cta-band p { line-height: 1.6; margin: 0 0 1.25rem; }

.cta-actions {
  display: flex;
  flex-wrap: wrap;
  gap: .75rem;
  justify-content: center;
}

.button {
  display: inline-block;
  background: var(--brand);
  color: #fff;
  font-family: var(--heading);
  font-weight: 700;
  text-decoration: none;
  padding: .875rem 1.5rem;
  border-radius: var(--radius);
  /* 44px minimum height for a finger, per WCAG 2.1 target size. */
  min-height: 44px;
  line-height: 1.5;
}

.button:hover { background: var(--brand-dark); }

.button-ghost {
  background: transparent;
  color: var(--brand);
  border: 2px solid var(--brand);
  padding: calc(.875rem - 2px) calc(1.5rem - 2px);
}

.button-ghost:hover { background: var(--brand); color: #fff; }

/* ── The footer's navigation ─────────────────────────────────────────────── */

.footer-nav {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(11rem, 1fr));
  gap: 1.75rem;
  padding-bottom: 2rem;
  margin-bottom: 1.5rem;
  border-bottom: 1px solid rgba(255, 255, 255, .18);
  text-align: left;
}

.footer-nav h3 {
  font-size: .8125rem;
  text-transform: uppercase;
  letter-spacing: .06em;
  margin: 0 0 .75rem;
}

.footer-nav ul { list-style: none; margin: 0 0 .5rem; padding: 0; }
.footer-nav li { margin-bottom: .5rem; }
.footer-nav a { text-decoration: none; }
.footer-nav a:hover { text-decoration: underline; }
.footer-nav p { margin: .25rem 0 0; }
.footer-phone { font-weight: 700; }

/*
 * Someone who has said they are sensitive to motion is told, and the site
 * stops moving. Nothing here animates much, but a future addition should not
 * have to remember.
 */
@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: .01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: .01ms !important;
    scroll-behavior: auto !important;
  }
}

/*
 * Windows high contrast mode replaces every colour with the user's own. Borders
 * drawn with a background rather than a border vanish entirely, so anything
 * load-bearing gets a real outline here.
 */
@media (forced-colors: active) {
  .button, .button-ghost { border: 2px solid ButtonText; }
  .claim-card { border: 1px solid CanvasText; }
  .site-nav a[aria-current="page"] { border-bottom: 2px solid LinkText; }
}

/* The claim grid on the front page. Same cards as /claims, on a tinted band so
 * it reads as a distinct section rather than more of the story above it. */
.claims-home {
  background: var(--bg-soft);
  border-top: 1px solid var(--line);
  padding: 3rem 1.25rem;
}

.claims-home-inner { max-width: 62rem; margin: 0 auto; }
.claims-home h2 { font-size: clamp(1.5rem, 3.5vw, 2rem); margin: 0 0 .5rem; }
.claims-home-intro { color: var(--ink-soft); margin: 0 0 1.75rem; max-width: 40rem; line-height: 1.6; }

/* ── The header, rebuilt around the phone number ───────────────────────────────
 *
 * Logo left, nav in the middle, phone right. The number is the highest-value
 * thing on the page for this audience — plenty of people who have just been
 * diagnosed with something would rather talk than type — and it was wrapping
 * onto a line of its own beneath the logo, reading as an afterthought, because
 * three social icons were taking the space. The icons moved to the footer.
 */
.site-header-inner {
  display: flex;
  align-items: center;
  gap: 1rem 1.5rem;
  flex-wrap: wrap;
}

.site-nav { margin-right: auto; }

.site-phone {
  /* Always pushed right — on one line it sits opposite the logo, and when the
   * header wraps at the awkward widths between a phone and a laptop it lands
   * at the right of its own row rather than adrift under the logo. */
  margin-left: auto;
  display: flex;
  flex-direction: column;
  align-items: flex-end;
  text-decoration: none;
  background: var(--brand);
  color: #fff;
  padding: .5rem 1.125rem;
  border-radius: var(--radius);
  min-height: 44px;
  justify-content: center;
}

.site-phone:hover { background: var(--brand-dark); }

.site-phone-label {
  font-size: .6875rem;
  text-transform: uppercase;
  letter-spacing: .06em;
  opacity: .85;
  line-height: 1.2;
}

.site-phone-number {
  font-family: var(--heading);
  font-weight: 700;
  font-size: 1.0625rem;
  line-height: 1.25;
  white-space: nowrap;
}

/* On a phone the nav goes full width under the logo, and the call button sits
 * beside the logo where a thumb can reach it without scrolling. */
@media (max-width: 47.9375rem) {
  .site-nav {
    order: 3;
    flex-basis: 100%;
    margin-right: 0;
    border-top: 1px solid var(--line);
    padding-top: .25rem;
  }
  .site-phone-label { display: none; }
}

/* In the footer the icons are decoration, not navigation. */
.site-footer .site-social { margin-top: 1rem; }

/* ── The header on a phone ────────────────────────────────────────────────────
 *
 * It was taking 490px of an 812px screen before a word of content: a 172px
 * logo, then the call button on a row of its own, then the nav across two more.
 * Sixty per cent of the first screen spent on furniture.
 *
 * Logo and call button share the top row; the nav sits under them, tight. The
 * whole header is now about 130px.
 */
@media (max-width: 30rem) {
  .site-header-inner { padding: .625rem .875rem; gap: .5rem .75rem; }

  .site-logo img { width: 132px; }

  .site-phone {
    padding: .5rem .75rem;
    /* Still 44px tall for a thumb, just not wide. */
    min-height: 44px;
  }

  .site-phone-number { font-size: .9375rem; }

  .site-nav { padding-top: .125rem; }

  .site-nav ul { gap: 0 .875rem; }

  .site-nav a { font-size: .875rem; padding: .5rem 0; }
}

/* Between a small phone and a tablet, the same idea with a little more room. */
@media (min-width: 30.0625rem) and (max-width: 47.9375rem) {
  .site-logo img { width: 150px; }
}

/* ── Focus, made visible on every background ─────────────────────────────────
 *
 * The ring was `3px solid var(--focus)` and `--focus` is the brand maroon —
 * the same colour as the hero band it sits on. Measured contrast against that
 * background: 1.00:1. Invisible. A keyboard user on the hero, which is every
 * page, could not see where they were. WCAG 2.1 AA 2.4.7 and 1.4.11.
 *
 * Two rings instead of one: a dark inner and a white outer. One of them always
 * contrasts, whatever is behind it, and no page has to remember to override
 * anything.
 */
:focus-visible {
  outline: 3px solid #1a1a1a;
  outline-offset: 2px;
  box-shadow: 0 0 0 6px #ffffff;
  border-radius: 2px;
}

/* On the maroon band the order flips: white nearest the element, dark outside,
 * so the bright ring reads against the dark ground. */
.hero :focus-visible,
.cta-band :focus-visible,
.site-phone:focus-visible,
.site-footer :focus-visible {
  outline: 3px solid #ffffff;
  outline-offset: 2px;
  box-shadow: 0 0 0 6px rgba(0, 0, 0, .55);
}

/* Windows high contrast draws its own ring; ours would just fight it. */
@media (forced-colors: active) {
  :focus-visible { outline: 3px solid Highlight; box-shadow: none; }
}

/* ── Form field borders ──────────────────────────────────────────────────────
 *
 * `#d9dde2` on white is 1.36:1. WCAG 1.4.11 asks 3:1 for the boundary of a
 * control, because a field you cannot find is a field you cannot fill in.
 * `#767b82` measures 4.0:1 and still reads as a quiet grey.
 */
input, select, textarea, .q-option {
  border-color: #767b82;
}

/* The thin rule over the hero note was 1.66:1 on maroon. */
.hero-note { border-top-color: rgba(255, 255, 255, .55); }

/*
 * A skip-link target needs `tabindex="-1"` or focus never moves — the viewport
 * scrolls and the next Tab starts again from the top of the document, which is
 * the classic silent skip-link failure. But a container that can hold focus
 * should not draw a ring when somebody merely clicks inside it.
 */
main[tabindex="-1"]:focus { outline: none; box-shadow: none; }
main[tabindex="-1"]:focus-visible { outline: 3px solid #1a1a1a; outline-offset: -3px; box-shadow: none; }

/* Present to a screen reader, absent to everyone else. Used where a heading is
 * needed for structure but would be noise on the page. */
.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip: rect(0 0 0 0);
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}

/* A heading inside <summary> must not inherit block layout, or the disclosure
 * marker and the text stop sharing a line. */
.faq-item summary h3 {
  display: inline;
  font-size: inherit;
  font-weight: inherit;
  margin: 0;
}

.footer-nav h2 {
  font-size: .8125rem;
  text-transform: uppercase;
  letter-spacing: .06em;
  margin: 0 0 .75rem;
}

/* ── A claim page's own content ─────────────────────────────────────────────── */

.tort-body {
  padding: 3rem 1.25rem;
  border-top: 1px solid var(--line);
}

.tort-body-inner { max-width: 46rem; margin: 0 auto; }
.tort-body .page-section:first-child { margin-top: 0; }
.tort-body-cta { margin-top: 2.5rem; }

/* ── The error summary ───────────────────────────────────────────────────────
 *
 * Per-field messages alone work for somebody who can see the whole form at
 * once. On a phone, with a screen reader, or with three problems spread down a
 * long form, they do not: you fix the one you were sent to, submit, and get
 * sent somewhere else. This says how many there are and links to each.
 */
.error-summary {
  border: 2px solid var(--error);
  border-left-width: 6px;
  border-radius: var(--radius);
  padding: 1rem 1.125rem;
  margin: 0 0 1.25rem;
  background: #fdf3f2;
}

.error-summary h2 {
  font-size: 1.0625rem;
  margin: 0 0 .5rem;
  color: var(--error);
}

.error-summary ul { margin: 0; padding-left: 1.25rem; }
.error-summary li { margin-bottom: .375rem; line-height: 1.5; }

.error-summary a {
  color: var(--error);
  /* Underlined, not just coloured: the distinction cannot rest on red alone
   * when the people reading it may not see red. */
  text-decoration: underline;
  font-weight: 600;
}

.error-summary[hidden] { display: none !important; }

/* ── The tablet dead zone ─────────────────────────────────────────────────────
 *
 * The hero stays one column until 62rem, so between a tablet in portrait and a
 * small laptop the form card rendered the full width of the page — text inputs
 * three-quarters of a metre wide, which nothing breaks but nobody wants. There
 * is plenty of room at 48rem for the fields to sit in pairs and for the card to
 * stop short of the edges.
 */
@media (min-width: 48rem) and (max-width: 61.9375rem) {
  .hero-grid { max-width: 40rem; margin-inline: auto; }

  /* An input is comfortable up to about 30rem and unreadable much past it. */
  .hero-form input,
  .hero-form select,
  .hero-form textarea { max-width: 32rem; }

  .hero-copy h1 { max-width: 30ch; }
  .hero-copy .subhead { max-width: 46ch; }

}

/* ── Dark mode ────────────────────────────────────────────────────────────────
 *
 * Worth the effort here specifically. A lot of this traffic arrives late at
 * night from somebody who has just been given a diagnosis and cannot sleep, on
 * a phone, in a dark room. A page that flares white at that moment is a small
 * cruelty and it is entirely avoidable.
 *
 * The neutral scale inverts; the brand does not. Maroon on near-black still
 * reads, and changing it would make the site look like somebody else's.
 * `color-scheme` is what tells the browser to darken its own furniture —
 * scrollbars, form controls, the address bar on iOS.
 */

/* ── The client portal ───────────────────────────────────────────────────────
 *
 * A buyer reads these tables to decide whether to argue about a lead, so the
 * numbers have to be scannable and the sentences beside them have to be the
 * thing your eye lands on second. The score column is fixed-width and tabular
 * so a column of +8 / -20 lines up.
 */
.portal-table {
  width: 100%;
  border-collapse: collapse;
  margin: 0 0 1rem;
  font-size: .9375rem;
}

.portal-table th,
.portal-table td {
  text-align: left;
  padding: .625rem .75rem;
  border-bottom: 1px solid var(--line);
  vertical-align: top;
}

.portal-table thead th {
  font-size: .8125rem;
  text-transform: uppercase;
  letter-spacing: .04em;
  color: var(--ink-soft);
  border-bottom-width: 2px;
}

.portal-table tbody tr:hover { background: var(--bg-soft); }

/* Wide tables scroll inside themselves rather than pushing the page sideways
 * on a phone. */
.portal-scroll { overflow-x: auto; }

.portal-table .points {
  font-variant-numeric: tabular-nums;
  font-weight: 600;
  white-space: nowrap;
  width: 4.5rem;
}

/* Colour is a second signal, never the only one: the sign is in the number
 * itself, so this still reads correctly to somebody who cannot see the hue. */
.portal-table .points.bad { color: var(--error); }
.portal-table .points.good { color: #14713c; }

.portal-note {
  font-size: .9375rem;
  color: var(--ink-soft);
  border-left: 3px solid var(--line);
  padding-left: .75rem;
}

/* The consent wording, quoted verbatim on a lead.
 *
 * Set apart deliberately: it is the one block on the page that is not ours —
 * it is what the claimant was shown, reproduced exactly — and it should not
 * read as prose we wrote about them. */
.portal-quote {
  margin: 1rem 0;
  padding: .875rem 1rem;
  background: var(--bg, #f5f7fa);
  border-left: 3px solid var(--brand, #8d021f);
  border-radius: 0 var(--r, 6px) var(--r, 6px) 0;
  font-size: .9375rem;
  line-height: 1.6;
}

.badge {
  display: inline-block;
  font-size: .8125rem;
  font-weight: 600;
  letter-spacing: .02em;
  padding: .1875rem .5rem;
  border-radius: 999px;
  border: 1px solid var(--line);
  background: var(--bg-soft);
  color: var(--ink-soft);
}

.badge-accept { background: #e7f4ec; border-color: #a7d3ba; color: #14713c; }
.badge-review { background: #fdf3e0; border-color: #e6c98a; color: #7a5308; }
.badge-reject { background: #fbeae9; border-color: #e3b3af; color: #93211a; }


/* Invoice status. `issued` deliberately reads as "waiting on you" rather than
 * as an error — it is an ordinary state, not a problem. */
.badge-issued { background: #eef2f7; border-color: #c3cede; color: #34496b; }
.badge-paid { background: #e7f4ec; border-color: #a7d3ba; color: #14713c; }
.badge-void { background: #f1f3f5; border-color: #d6dade; color: #6b7178; text-decoration: line-through; }


/* ── The B2B pages ───────────────────────────────────────────────────────────
 *
 * The form reuses `.field` and `.submit` from the claimant form deliberately —
 * a buyer who has already looked at the front of the site should recognise
 * this as the same company, and a second set of form styles is a second place
 * to get the focus ring wrong.
 */
.partner-form { max-width: 34rem; }
.partner-form .optional { font-weight: 400; color: var(--ink-soft); }
.form-note { font-size: .875rem; color: var(--ink-soft); margin-top: .75rem; }

/* The API examples. Scrolls inside itself: a long line of JSON must never be
 * the reason the whole page scrolls sideways on a phone. */
.code-block {
  background: var(--bg-soft);
  border: 1px solid var(--line);
  border-radius: var(--radius);
  padding: 1rem;
  overflow-x: auto;
  font-size: .8125rem;
  line-height: 1.6;
  margin: 0 0 1rem;
}

.code-block code {
  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
  white-space: pre;
}


/* The month picker, on the client's own report. */
.month-picker { display: flex; align-items: center; gap: .5rem; margin: 0 0 1.5rem; }
.month-picker label { margin: 0; font-weight: 600; }
.month-picker select { width: auto; min-width: 12rem; }

@media (prefers-color-scheme: dark) {
  :root {
    color-scheme: dark;

    --ink: #e8e6e3;
    --ink-soft: #b4b0ab;
    --line: #3a3d42;
    --bg: #16181c;
    --bg-soft: #1e2126;

    /* Lifted off the brand maroon, which is too dark to read against a dark
     * page. Measured 7.1:1 on --bg. */
    --brand-text: #f2909f;
    --error: #ff8b82;

    /*
     * The tinted surface, which was NOT redefined here and broke the form.
     *
     * `--brand-tint` is a pale pink. In dark mode `--ink` becomes near-white
     * while this stayed light, so `.tort-questions` — the whole block of
     * questions a claimant has to answer — rendered near-white text on pale
     * pink: labels invisible, and the answer chips dark because THEY inherit
     * `--bg` and were therefore correct. A partner reported it as "your website
     * looks like this" with a screenshot of an unusable MVA form.
     *
     * A token defined for one theme and not the other is the whole bug class.
     * The same maroon bias as the light tint, carried to a dark ground:
     * `--ink` measures 13.6:1 on it.
     */
    --brand-tint: #241a1e;
  }

  body { background: var(--bg); color: var(--ink); }

  .site-header { background: var(--bg); }

  /*
   * The logo is a single black path with no fill declared, so on a dark header
   * it was black on near-black — effectively invisible. Inverting a pure-black
   * mark gives pure white, which is what the printed version of this lockup
   * uses on dark anyway.
   */
  .site-logo img { filter: invert(1); }
  .site-nav a { color: var(--ink); }
  .site-nav a:hover,
  .site-nav a[aria-current="page"] { color: var(--brand-text); border-bottom-color: var(--brand-text); }

  /* The hero keeps its maroon: it is the one surface that was already dark. */
  .claims-home, .cta-band { background: var(--bg-soft); border-top-color: var(--line); }
  .cta-band h2 { color: var(--ink); }

  .claim-card { background: var(--bg-soft); border-color: var(--line); }
  .claim-card h3 a { color: var(--brand-text); }
  .claim-card:hover { border-color: var(--brand-text); }

  .hero-form,
  .page, .legal { background: transparent; }
  .hero-form form { background: var(--bg-soft); }

  input, select, textarea {
    background: var(--bg);
    color: var(--ink);
    border-color: #6f747b;
  }

  ::placeholder { color: #8b8f96; }

  .page-section h2, .legal-section h2 { color: var(--brand-text); }

  .faq-item { border-bottom-color: var(--line); }
  .faq-item summary::after { color: var(--brand-text); }

  .error-summary { background: #2a1a1a; border-color: var(--error); }
  .error-summary h2, .error-summary a { color: var(--error); }

  .tort-body { border-top-color: var(--line); }

  /* The buttons stay brand-filled — they are the one place the maroon should
   * still be a block of colour, and white on it is 8.6:1 either way. */
  .button-ghost { color: var(--brand-text); border-color: var(--brand-text); }
  .button-ghost:hover { background: var(--brand-text); color: #16181c; }

  /* The dark ring disappears on a dark page; the light one leads. */
  :focus-visible {
    outline: 3px solid #ffffff;
    box-shadow: 0 0 0 6px rgba(0, 0, 0, .8);
  }

  .portal-table thead th { color: var(--ink-soft); }
  .portal-table tbody tr:hover { background: var(--bg-soft); }
  .portal-table .points.good { color: #6fcf97; }

  .badge-accept { background: #16301f; border-color: #2f6b45; color: #8fdcae; }
  .badge-review { background: #332711; border-color: #7a5f22; color: #ecc474; }
  .badge-reject { background: #331a19; border-color: #7a3330; color: #ff9b93; }

  .badge-issued { background: #1b2431; border-color: #33465f; color: #a8c3e8; }
  .badge-paid { background: #16301f; border-color: #2f6b45; color: #8fdcae; }
  .badge-void { background: #212429; border-color: #3d4249; color: #9aa0a6; }

  .code-block { background: #12151a; border-color: var(--line); }
}