/* ==========================================================================
   footer.css — the closing block. Loaded by index.html and profile.html.

   Two changes, and they are one change: the footer moves off purple onto the
   hero's neutral grey ink, and the newsletter band moves inside it.

   WHY THE GREY. hero-map.css states the rule in its own comment: the stage
   is "neutral grey ink with two lighter washes, so purple means 'an agency
   works here' rather than being what the page is made of." The footer was the
   last full-bleed purple surface, which put that claim back in doubt on the way
   out. The page now opens and closes on the same environment and every purple
   between them belongs to a member. The values below are quoted from
   .map-stage, not re-picked - if that recipe changes, change it here too.

   WHY THE BAND MOVED. It was a white full-bleed block between a white section
   and a hard purple edge, with a hairline above it and nothing below: no ground
   of its own and no relationship to either neighbour. Inside the footer it
   inherits a ground for free, and the subordination that brief-form.css was
   holding up with styling ("no card, no tinted ground, an outlined button")
   is now carried by placement instead, which is sturdier.

   Loaded LAST and scoped under .site-footer, so it only ever overrides
   brief-form.css inside the footer. profile.html loads it too: its own closing
   block used to be the closer, then briefly carried this band as a section of
   the page, and both pages now end on the same footer with the same band in
   the same place.
   ========================================================================== */

/* -- the ground ---------------------------------------------------------- */
/* Quoted from .map-stage in hero-map.css. The washes are re-aimed for a wide
   short block rather than a tall stage: one along the top edge where the band
   sits, one trailing off bottom-right. */
.site-footer{
  background:
    radial-gradient(90% 120% at 22% 0%, #2A2E36 0%, transparent 58%),
    radial-gradient(70% 100% at 88% 100%, #23262D 0%, transparent 70%),
    #14161A;
}

/* The longitude ramp stays. Against grey it is now the only purple on the edge
   between the page and the footer, which is the job it was always doing and
   could not do against a purple ground. */

/* -- the type ------------------------------------------------------------
   base.css sets every resting string in the footer - the blurb, the column
   links, the copyright, the legal links - to --lavender, because it was written
   for a --plum ground where lavender is simply "light text". On grey it stops
   being light text and starts being PURPLE text, in seven places at once, which
   is the same failure the grey ground was chosen to fix one level up: purple
   should mean "an agency works here", not be what the page is made of.

   So the resting state goes neutral and purple is spent only where it means
   something - the longitude ramp, and the focus ring. Hover already went to
   --white in base.css and is left alone.

   White at two opacities rather than two new colours, which is the move
   .footer-note already makes with its own opacity:.85. Scoped to .site-footer,
   so nothing leaks. Measured against the #14161A base: --f-text 10.2:1,
   --f-quiet 5.8:1. */
.site-footer{
  --f-text:rgb(255 255 255 / .74);    /* body copy and column links */
  --f-quiet:rgb(255 255 255 / .55);   /* the note and the legal line */
  color:var(--f-text);
}
.site-footer .footer-blurb,
.site-footer .footer-col a,
.site-footer .footer-legal a{color:var(--f-text)}
.site-footer .footer-note{color:var(--f-quiet);opacity:1}

/* --purple-deep on #14161A is about 1.7:1 - a focus ring nobody can see. The
   footer takes --lavender, which clears 3:1 against this ground several times
   over. This and the ramp are now the ONLY purple down here, which is what
   makes the ring read as a state rather than as more of the same. */
.site-footer :focus-visible{outline-color:var(--lavender)}

/* -- the newsletter band is gone (2026-08-28, client direction) -----------
   Everything that was here dressed a subscribe band for the dark ground: the
   hairline under it, its 48/44 padding, the white heading, the --f-text deck,
   the two-row note, and later the grid track that lined its button up with the
   columns below. The band was removed from every footer and all of it went with
   it, rather than being left as rules matching no markup.

   THE FOOTER NOW OPENS ON .footer-top. Nothing here needs to replace the band's
   padding - .footer-top pays its own, and the ramp is still the edge at the top.

   newsletter.html is reached from the "Newsletter" item in .ins-nav on the five
   light pages, and from "The market notes" in the Network column below. That
   second one is the only link every page has. Do not tidy it out of the list.
   -------------------------------------------------------------------------- */

/* -- the footer's two rows share one set of column edges ------------------
   It was three rows, and the band was the first of them. They were each laid
   out on their own terms, so nothing above lined up with anything below:
   Privacy/Terms sat flush to the wrap's right edge while the last column of
   links started 300px short of it. Measured at 1544: content runs 96..1448,
   brand 96..456, columns 496..1448.

   Both remaining rows use the SAME split .footer-top already declares - a 360px
   identity block, a 40px gutter, then a three-column track. Nothing here
   invents a measurement; flex:1 1 300px/max-width:360px and flex:2 1 480px are
   lifted from .footer-brand and .footer-cols so the rows cannot drift.
   -------------------------------------------------------------------------- */
.site-footer .footer-base{
  display:flex;flex-wrap:wrap;align-items:baseline;
  gap:var(--s3) var(--s10);
}
.site-footer .footer-base .footer-note{flex:1 1 300px;max-width:360px}
.site-footer .footer-base-cols{
  flex:2 1 480px;
  display:grid;grid-template-columns:repeat(3,1fr);gap:var(--s6);
}
/* Column 3, and pushed to the FAR side of it. The track alone put the list box
   in column 3 but left the links themselves ranged left inside it, so the text
   stopped about 180px short of the edge the link columns land on - the box was
   aligned and the thing you can actually see was not. Ranged right,
   Privacy/Terms close on the same vertical as the right edge of the columns
   above them. (This once had a third thing to agree with, the band's Subscribe
   button; the band is gone and the alignment it shared is not.) */
.site-footer .footer-legal{grid-column:3;margin-left:0;justify-content:flex-end}

/* The 1260px block that used to close this file went with the band: it existed
   to give the band's note the whole track once two of three columns stopped
   supplying the 520px its second line needed. Nothing else in the footer has a
   line with that constraint. */