/*
 * Stranieri Propiedades — the approved design.
 *
 * GENERATED by tools/build_theme_css.py from design/index.html. Do not edit by hand:
 * the mockup is what the client approved, so the mockup is the source. Change the
 * design there, regenerate, and `tools/validate_day10.py` will confirm the two agree.
 *
 * Loaded only on the Stranieri hosts. iProp never sees this file.
 */
/* ============================================================
   Stranieri Propiedades — design mockup, milestone 1 day 4
   Palette: the brand navy #01074F read out of the client's own
   CorelDRAW palette. Neutrals are biased toward it, never grey.
   ============================================================ */
:root{
  /* Light ground, by his instruction on 12 Nov: "me gustaría que el fondo sea
     claro, el azul no me termina de gustar — podemos resaltar el logo de otra
     forma". So the navy stops being the field and becomes the accent: it now
     appears only on the logo, the buttons, the badges and the type. The
     neutrals are warm rather than blue-grey, which is what gives a white page
     the paper feel of the reference he chose (elliman.com) instead of the
     cold grey of a template. */
  --navy:#01074F;
  --navy-deep:#000730;
  --navy-tint:#1C2577;
  --ground:#FBFAF7;
  --surface:#FFFFFF;
  --surface-2:#F5F3EE;
  --ink:#14161F;
  --muted:#5E6172;
  --line:#E3DFD7;
  --line-soft:#EFECE5;
  --on-navy:#FFFFFF;
  --on-navy-dim:#B9BDD8;
  --venta:#01074F;
  --alquiler:#0C5F54;
  --alquiler-soft:#E3F1EE;
  /* The height of the header once it has stuck and compacted: 9 + 58 + 9 + 1.
     Anything that sticks BELOW the header has to clear it, or it slides
     underneath -- which is what `.filters` and `.aside` would now do, since
     un-trapping .frame is what finally let them stick at all. */
  --head-stuck:78px;
  --warn:#8A5A00;
  --shadow:0 1px 2px rgba(20,22,31,.05), 0 10px 30px -14px rgba(20,22,31,.18);
  --radius:10px;
  color-scheme:light;
  --sans:'Archivo', 'Segoe UI', system-ui, sans-serif;
  --serif:'Source Serif 4', Georgia, serif;
}
/* No dark variant, deliberately. He asked for a light site — "me gustaría que el
   fondo sea claro" — so the page commits to that look and paints it explicitly
   rather than following the viewer's theme. A dark render would show him a site
   he did not approve, and would also put the navy-on-white logo on a dark bar. */

*{box-sizing:border-box}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
  font-size:15px;line-height:1.5;-webkit-text-size-adjust:100%}
img{display:block;max-width:100%}
button,select,input,textarea{font:inherit;color:inherit}
a{color:inherit}
:focus-visible{outline:2px solid var(--navy-tint);outline-offset:2px}@media (prefers-reduced-motion:reduce) {*{transition:none!important;animation:none!important}}

/* ---------- mockup chrome (not part of the site) ---------- */


/* ---------- the device frame ---------- */
/* Full-bleed on the desktop view: the site fills the screen the way it will in
   a real browser, rather than sitting in a centred card that makes everything
   inside it look smaller than it is. The phone view keeps its device frame,
   because that is the point of the phone view. */

/* `overflow:hidden` here, 2026-11-17: it makes .frame a scroll container, and a
   scroll container ancestor is where `position:sticky` sticks. The header would
   have stuck to a box that never scrolls -- i.e. not at all -- and nothing would
   have looked broken, it simply would not have worked. `overflow-x:clip` clips the
   same way without creating one, which is the entire reason `clip` exists. The
   y axis must be explicitly `visible`: left to default it inherits the clip and
   the scroll container comes straight back. */
.frame{container-type:inline-size;min-width:0;width:100%;max-width:none;background:var(--surface);
  border:0;border-radius:0;overflow-x:clip;overflow-y:visible}
.urlbar{display:flex;align-items:center;gap:8px;padding:7px 12px;background:var(--surface-2);
  border-bottom:1px solid var(--line-soft);font-size:12.5px;color:var(--muted);
  overflow:hidden;white-space:nowrap}
.urlbar svg{flex:none;color:var(--alquiler)}
.urlbar b{color:var(--ink);font-weight:500;flex:none}
.urlbar span{flex:1 1 auto;min-width:0;overflow:hidden;text-overflow:ellipsis}

/* ---------- site header ----------
   "Podemos resaltar el logo de otra forma." The plaque is gone with the navy
   field. On a white bar the navy mark is the darkest thing on the page, which
   is a stronger way to carry it than a box was — and it is bigger than before,
   which is what he actually asked for. */
/* "la menu debe estar siempre visible" and "un fondo tenue y transparente detras"
   -- 2026-11-17. The bar sticks to the top of the viewport on every page and carries
   a translucent ground rather than a solid one, so the page reads THROUGH it as it
   scrolls. --surface is #FFFFFF, so the glass is that colour at 72%: a bar that
   matched --surface exactly would be opaque and not what he asked for. */
.site-head{color:var(--ink);position:sticky;top:0;z-index:30;
  background:rgba(255,255,255,.72);
  -webkit-backdrop-filter:saturate(1.7) blur(14px);backdrop-filter:saturate(1.7) blur(14px);
  border-bottom:1px solid var(--line-soft);transition:background .2s ease,box-shadow .2s ease}
/* Browsers without backdrop-filter (older Firefox with it disabled) would show the
   page sliding under unreadable 72% white. They get an opaque bar instead: less
   pretty, still legible, which is the right way round. */
@supports not ((backdrop-filter:blur(1px)) or (-webkit-backdrop-filter:blur(1px))) {
  .site-head{background:var(--surface)}
  .frame.on-home .site-head.is-stuck{background:var(--surface)}}
/* Once it has left the top of the document it is floating over content, so it earns
   a shadow and gives back the height its 94px mark was taking from a scrolled page. */
.site-head.is-stuck{box-shadow:0 10px 30px -18px rgba(20,22,31,.45)}
/* The compaction is deliberately GENTLE. Every pixel the bar loses here is a pixel the
   whole page jumps upward at the moment it sticks, because the bar sits in normal flow.
   At 94px down to 58px that jump was 54px and it read as a shudder; 76px keeps the mark
   substantial — which he has asked for three times — and halves the movement. The other
   half of that fix is the hysteresis in stranieri.js, which stops the two thresholds
   chasing each other. */
.site-head.is-stuck .head-in{padding-top:13px;padding-bottom:13px}
.site-head.is-stuck .logo{height:76px}
.head-in,.logo{transition:padding .2s ease,height .2s ease}@media (prefers-reduced-motion:reduce) {.site-head,.head-in,.logo{transition:none}}
/* "El menú no debería tenerlo, podríamos hacer los botones flotantes." On the
   home screen the bar carries no mark and no ground of its own: it lifts off
   the page and floats over the photograph, which is what both references he
   named do on arrival. The stage reserves room for it so nothing is covered. */
.frame.on-home .site-head{position:sticky;top:0;z-index:30;background:transparent;
  -webkit-backdrop-filter:none;backdrop-filter:none;box-shadow:none;
  border-bottom:0;margin-bottom:calc(-1 * var(--head-h, 82px))}
/* THE ONE CASE THAT NEEDS JAVASCRIPT. On the home page the bar is white text over a
   photograph. Stick it and it keeps that white text over the white sections below,
   where it would be invisible. So `is-stuck` is set from the scroll position and the
   bar changes clothes: the glass comes back, the mark reappears (the hero's copy has
   scrolled away, so there is nothing left to duplicate) and the type goes navy. */
.frame.on-home .site-head.is-stuck{background:rgba(255,255,255,.72);
  -webkit-backdrop-filter:saturate(1.7) blur(14px);backdrop-filter:saturate(1.7) blur(14px);
  border-bottom:1px solid var(--line-soft);
  box-shadow:0 10px 30px -18px rgba(20,22,31,.45)}
.frame.on-home .site-head.is-stuck .logo{display:block}
.frame.on-home .site-head.is-stuck .nav a{color:var(--muted);text-shadow:none}
.frame.on-home .site-head.is-stuck .nav a:hover{background:var(--surface-2);color:var(--ink)}
.frame.on-home .site-head.is-stuck .nav a[aria-current="page"]{color:var(--navy);font-weight:600}
.frame.on-home .site-head.is-stuck .nav a.btn-wa{background:var(--surface);color:var(--navy);
  border-color:var(--navy);-webkit-backdrop-filter:none;backdrop-filter:none}
.frame.on-home .site-head.is-stuck .nav a.btn-wa:hover{background:var(--navy);color:#fff}
.frame.on-home .site-head.is-stuck .burger{background:var(--surface-2);
  border-color:var(--line);color:var(--ink)}
.frame.on-home .site-head .logo{display:none}
.frame.on-home .nav a{color:rgba(255,255,255,.92);text-shadow:0 1px 10px rgba(0,0,0,.55)}
.frame.on-home .nav a:hover{background:rgba(255,255,255,.16);color:#fff}
.frame.on-home .nav a[aria-current="page"]{color:#fff;font-weight:600;
  background:rgba(255,255,255,.18)}
.frame.on-home .nav a[aria-current="page"]::after{background:#fff}
.frame.on-home .site-head.is-stuck .nav a[aria-current="page"]::after{background:var(--navy)}
.frame.on-home .nav a.btn-wa{background:rgba(10,12,20,.44);color:#fff;
  border-color:rgba(255,255,255,.6);backdrop-filter:blur(6px);
  -webkit-backdrop-filter:blur(6px);text-shadow:none}
.frame.on-home .nav a.btn-wa:hover{background:#fff;color:var(--navy)}
.frame.on-home .burger{background:rgba(10,12,20,.44);border-color:rgba(255,255,255,.5);color:#fff}
/* On the home page the bar floats over the hero, so the open menu is dark glass —
   and it overlays too: `margin-top` would push the hero down, which is the thing the
   overlay exists to stop. */
.frame.on-home .site-head.open .nav{background:rgba(10,12,20,.88);
  border-radius:0 0 12px 12px;backdrop-filter:blur(8px);
  -webkit-backdrop-filter:blur(8px);padding:10px 14px 14px;margin-top:0}
/* The bar stays in flow — absolute positioning anchored it to the frame's top,
   which is where the mock browser bar lives, and it disappeared under it. A
   negative margin of exactly its own height lets the picture rise behind it
   instead, and the stage pads its content clear by the same amount. The height
   is measured and published as --head-h, not guessed: it changes with the
   WhatsApp button's line-height and with the phone breakpoint. */
.frame.on-home .hero-in{padding-top:calc(var(--head-h, 82px) + 24px)}
/* The mark is back in the bar on every screen: the hero is centred now, so the
   bar is the only place it appears and there is nothing to duplicate. */
.head-in{padding:18px 28px;display:flex;align-items:center;gap:18px}
/* The mark is the strongest asset he has and he has asked for it bigger three
   times. At 94 px it is the dominant object in the bar rather than a label
   beside the navigation — which is the whole point of a wordmark this fine. */
.logo{height:94px;width:auto;flex:none}@container (max-width:1200px) {.logo{height:78px}}
.nav{margin-left:auto;display:flex;gap:2px;align-items:center}
.nav a{position:relative;padding:9px 12px;border-radius:7px;text-decoration:none;font-size:14px;
  font-weight:500;color:var(--muted);transition:background .15s,color .15s}
.nav a:hover{background:var(--surface-2);color:var(--ink)}
.nav a[aria-current="page"]{color:var(--navy);font-weight:600;background:var(--surface-2)}
.nav a[aria-current="page"]::after{content:"";position:absolute;left:12px;right:12px;
  bottom:4px;height:2px;border-radius:2px;background:var(--navy)}
/* The WhatsApp button is an action, never a page: it must not grow a marker. */
.nav a.btn-wa[aria-current="page"]::after{display:none}
.nav a.btn-wa,.btn-wa{display:inline-flex;align-items:center;gap:8px;background:var(--surface);
  color:var(--navy);border:1.5px solid var(--navy);border-radius:8px;padding:11px 18px;
  font-weight:600;font-size:14px;cursor:pointer;text-decoration:none;margin-left:12px}
.nav a.btn-wa:hover{background:var(--navy);color:#fff}

/* He wants the WhatsApp button at the foot of the screen as well: this is the
   one action the whole site exists to produce, and on a phone the top bar is
   the part of the page a reader has already scrolled past. */
.wa-float{position:fixed;right:22px;bottom:22px;z-index:40;display:inline-flex;
  align-items:center;gap:9px;background:var(--alquiler);color:#fff;border:0;
  border-radius:999px;padding:14px 20px;font-weight:600;font-size:15px;cursor:pointer;
  text-decoration:none;box-shadow:0 14px 34px -12px rgba(12,95,84,.75)}
.wa-float:hover{filter:brightness(1.07)}
/* Raised on phones, on his instruction of 2026-11-14 ("subir el boton de
   whatsapp"): at bottom:14px it landed on the hero's search card and covered
   the Alquilar tab. 96px clears the card and still sits in thumb reach. */
@container (max-width:900px) {.wa-float{right:14px;bottom:96px;padding:13px 18px;font-size:14px}}
.btn-wa svg{flex:none}
.burger{margin-left:auto;display:none;background:var(--surface-2);border:1px solid var(--line);
  color:var(--ink);border-radius:7px;padding:9px 11px;cursor:pointer}@container (max-width:760px) {
  .nav{display:none;order:3}
  .burger{display:block;order:2}
  .head-in{padding:12px 14px;gap:10px;flex-wrap:wrap}
  .logo{height:60px}
  /* The burger opens the same nav, OVERLAID on the page rather than stacked under
     the bar. Changed 2026-11-14 at the client's request, after seeing it on his
     phone: pushing the hero down moved everything he was looking at, and over a
     transparent header on the home page it read as the layout breaking. An overlay
     leaves the page exactly where he left it. */
  .site-head.open .nav{display:flex;flex-direction:column;align-items:stretch;
    position:absolute;left:0;right:0;top:100%;z-index:40;
    margin:0;gap:2px;padding:10px 14px 14px;
    background:var(--surface);border-top:1px solid var(--line-soft);
    box-shadow:0 18px 40px -18px rgba(20,22,31,.45)}
  .site-head.open .nav a{padding:11px 10px;font-size:15px}
  .site-head.open .btn-wa{justify-content:center;margin-top:6px}

  /* THE OPEN MENU IS ALWAYS SOLID. "The text is hard to see" — 2026-11-17, and it was:
     the page showed straight through the panel.

     Three rules were competing for it. The home page paints the bar as dark glass over
     the photograph; `is-stuck` repaints it as WHITE glass once scrolled; and the open
     menu is a child of that bar. Scrolled down on the home page you got the dark-glass
     panel with the stuck state's dark navy type on it — dark on translucent dark.

     The menu is the one surface where legibility beats the effect, so it opts out of
     all of it: one opaque ground and one ink, whatever the bar above it is doing. The
     selectors are deliberately as specific as the rules they have to beat. */
  .site-head.open .nav,
  .frame.on-home .site-head.open .nav,
  .frame.on-home .site-head.is-stuck.open .nav{
    background:var(--surface);
    -webkit-backdrop-filter:none;backdrop-filter:none;
    border-radius:0 0 12px 12px;
    box-shadow:0 20px 44px -14px rgba(20,22,31,.55)}
  .site-head.open .nav a,
  .frame.on-home .site-head.open .nav a,
  .frame.on-home .site-head.is-stuck.open .nav a{
    color:var(--ink);text-shadow:none;background:transparent}
  .site-head.open .nav a[aria-current="page"],
  .frame.on-home .site-head.open .nav a[aria-current="page"]{
    color:var(--navy);background:var(--surface-2)}
  .site-head.open .nav a.btn-wa,
  .frame.on-home .site-head.open .nav a.btn-wa,
  .frame.on-home .site-head.is-stuck.open .nav a.btn-wa{
    background:var(--navy);color:#fff;border-color:var(--navy)}}@container (max-width:460px) {.logo{height:50px}}

/* ---------- screens ---------- */

.wrap{max-width:1320px;margin:0 auto;padding:0 32px}@container (max-width:900px) {.wrap{padding:0 18px}}@container (max-width:460px) {.wrap{padding:0 14px}}
/* ---------- section rhythm ----------
   Each block gets room and a ground of its own. Alternating the surface is what
   turns a long scroll into a sequence of places rather than one list that keeps
   going: you can tell where you are without reading a heading. */
section{padding:40px 0}
.sec{padding:84px 0}
.sec + .sec{padding-top:84px}@container (max-width:900px) {.sec{padding:44px 0}.sec + .sec{padding-top:44px}}
.sec--plain{background:var(--surface)}
.sec--tint{background:var(--ground)}
/* one inverted block, so the agency reads as a statement rather than a row */
.sec--deep{background:var(--navy);color:var(--on-navy)}
.sec--deep .eyebrow{color:var(--on-navy-dim)}
.sec--deep h2{color:var(--on-navy)}
.sec .sec-head{margin-bottom:26px}@container (max-width:900px) {.sec .sec-head{margin-bottom:18px}}@container (max-width:760px) {section{padding:26px 0}}

h1,h2,h3{font-weight:600;text-wrap:balance;margin:0}
h1{font-size:30px;line-height:1.18;letter-spacing:-.01em}
h2{font-size:21px;letter-spacing:-.005em}
h3{font-size:16px}@container (max-width:760px) {h1{font-size:23px}h2{font-size:18px}}
.eyebrow{font-size:11px;letter-spacing:.16em;text-transform:uppercase;color:var(--muted);
  font-weight:600}
.lede{font-family:var(--serif);font-size:17px;line-height:1.6;color:var(--muted);max-width:60ch}
.sec-head{display:flex;align-items:baseline;gap:14px;margin-bottom:18px}
.sec-head a{margin-left:auto;font-size:13.5px;font-weight:600;color:var(--navy-tint);
  text-decoration:none;white-space:nowrap}
/* One line under a heading, saying what the section is FOR. Added 2026-11-17: "it is
   not clear what these two sections are intended to convey". The two shortcut bands
   are navigation wearing the costume of content — same card, same photograph, same
   shape as a property — so a heading like "¿Qué estás buscando?" left the reader to
   work out that these were categories and not listings. A sentence costs one line and
   removes the guess. */
.sec-lede{margin:7px 0 0;font-size:14.5px;line-height:1.5;color:var(--muted);max-width:60ch}
.num{font-variant-numeric:tabular-nums}

/* ---------- the stage ----------
   He named two references, elliman.com and dacal.com.ar, and on arrival both
   do the same thing: one photograph fills the screen and everything else — the
   mark, the claim, the ways in — sits inside it rather than under it. That is
   the "sensación de estar inmerso" he is after, so the hero stopped being a
   band with a picture below it and became the picture.

   Height is viewport-relative but bounded, and svh not vh: on a phone vh counts
   the browser chrome that is about to scroll away, which is why these heroes so
   often sit 60px too tall on the first paint. */
.hero{position:relative;background:var(--ground);padding:0}
.herostage{position:relative;overflow:hidden;isolation:isolate;
  min-height:clamp(600px,88svh,1040px);display:flex}@container (max-width:900px) {.herostage{min-height:clamp(560px,100svh,920px)}}

.hero-in{position:relative;z-index:2;flex:1;display:flex;flex-direction:column;
  max-width:1320px;margin:0 auto;width:100%;padding:26px 32px 34px}@container (max-width:900px) {.hero-in{padding:18px 18px 158px}}
.hero-top{display:flex;align-items:flex-start;gap:16px}
.hero-mid{flex:1;display:grid;grid-template-columns:auto 1fr;gap:20px 52px;
  align-items:center;padding:14px 0}@container (max-width:1000px) {.hero-mid{gap:18px 34px}}@container (max-width:860px) {
  .hero-mid{grid-template-columns:1fr;justify-items:center;text-align:center;gap:16px}}
/* "Que sea del tamaño del círculo verde — es la firma del sitio." So the mark
   is the largest object on the first screen, roughly three times what it was.
   Sized in cqw, not vw: the frame is the container, and vw would measure the
   whole window — which means the phone preview inside a desktop window would
   render a 290px mark in a 392px frame. */
.hero-logo{height:clamp(104px,20cqw,300px);width:auto;flex:none;
  filter:drop-shadow(0 10px 36px rgba(0,0,0,.6))}
.hero-copy{min-width:0}@container (max-width:860px) {.hero-copy{text-align:center}}

/* ---------- the claim, typed ----------
   "Me gustaría que la frase apareciera como si se estuviera escribiendo."
   The real sentence stays in the DOM as the h1's accessible name, so a screen
   reader and a crawler never meet a half-written phrase — only the visible copy
   types. Under prefers-reduced-motion it is simply there. */
.hero-claim{font-family:var(--serif);font-weight:400;font-size:clamp(28px,4.1cqw,56px);
  line-height:1.1;letter-spacing:-.02em;margin:0;color:#fff;max-width:15ch;
  min-height:2.2em;text-shadow:0 2px 30px rgba(0,0,0,.5)}
.hero-claim em{display:block;font-style:italic}@container (max-width:860px) {.hero-claim{max-width:none;margin-inline:auto}}
.tw{display:inline;white-space:pre-wrap}
.tw.typing::after{content:"";display:inline-block;width:2px;height:.82em;
  margin-left:4px;vertical-align:-.06em;background:currentColor;
  animation:caret 1s steps(1,end) infinite}@keyframes caret {50%{opacity:0}}@media (prefers-reduced-motion:reduce) {.tw.typing::after{display:none}}

.hero-sub{font-size:16.5px;color:rgba(255,255,255,.92);margin:18px 0 0;max-width:46ch;
  line-height:1.55;text-shadow:0 1px 14px rgba(0,0,0,.5)}@container (max-width:900px) {.hero-sub{font-size:14.5px;margin-top:10px}}@container (max-width:860px) {.hero-sub{margin-inline:auto}}

.shot{position:absolute;inset:0;opacity:0;transition:opacity 1.8s cubic-bezier(.4,0,.2,1);z-index:0}
.shot img,.shot video{width:100%;height:100%;object-fit:cover;transform:scale(1.02)}
.shot.on{opacity:1}
.shot.on img,.shot.on video{animation:kb 14s ease-out forwards}@keyframes kb {from{transform:scale(1.04)}to{transform:scale(1.13) translate(-1.2%,-1.4%)}}
.shot-veil{position:absolute;inset:0;z-index:1;pointer-events:none;
  background:
    linear-gradient(to bottom,rgba(8,10,18,.70) 0%,rgba(8,10,18,.34) 26%,
      rgba(8,10,18,.44) 58%,rgba(8,10,18,.86) 100%),
    linear-gradient(to right,rgba(8,10,18,.54) 0%,rgba(8,10,18,.20) 48%,
      rgba(8,10,18,.32) 100%)}@media (prefers-reduced-motion:reduce) {.shot.on img,.shot.on video{animation:none}
  .shot{transition:none}}

/* Its own backing rather than a heavier scrim over everything: deepening the
   whole gradient to carry eight words would dull the photograph that is doing
   the selling. Light on purpose - measured against the real pixels behind the
   glyphs, 34% clears AA with room (the backdrop there is ~122/255 once the top
   of the scrim has done its work). */
.hc-label{font-size:10.5px;letter-spacing:.22em;text-transform:uppercase;font-weight:600;
  color:#fff;background:rgba(8,10,18,.34);padding:7px 12px;border-radius:999px;
  backdrop-filter:blur(3px);-webkit-backdrop-filter:blur(3px)}@container (max-width:460px) {.hc-label{letter-spacing:.14em;font-size:9.5px}}
.dots{margin-left:auto;display:flex;gap:6px;flex:none}
.dots button{width:7px;height:7px;padding:0;border-radius:50%;border:0;cursor:pointer;
  background:rgba(255,255,255,.55);transition:background .2s,width .2s}
.dots button[aria-current="true"]{background:#fff;width:22px;border-radius:4px}

/* ---------- hero search ----------
   Lower down, as he asked — it now sits at the foot of the picture rather than
   straight under the headline. Operation stays a forced choice of the two. */
.searchbar{background:var(--surface);color:var(--ink);border:1px solid var(--line);
  border-radius:var(--radius);margin:-36px 0 0;position:relative;z-index:3;
  padding:16px;display:grid;gap:10px;grid-template-columns:1fr 1fr 1fr auto;
  box-shadow:0 26px 60px -26px rgba(20,22,31,.55)}@container (max-width:900px) {.searchbar{margin-top:-24px}}
.opseg{grid-column:1/-1;display:flex;gap:4px;background:var(--surface-2);
  border:1px solid var(--line);border-radius:8px;padding:4px}
.opseg button{flex:1;background:none;border:0;border-radius:6px;padding:9px 6px;cursor:pointer;
  font-size:14px;font-weight:600;color:var(--muted);transition:background .15s,color .15s}
.opseg button[aria-pressed="true"]{background:var(--navy);color:#fff}
.opseg button[aria-pressed="true"].alq{background:var(--alquiler)}@container (max-width:1100px) {.searchbar{grid-template-columns:1fr 1fr}
  .searchbar .btn{grid-column:1/-1}}@container (max-width:460px) {.searchbar{grid-template-columns:1fr}
  .searchbar .btn{grid-column:1/-1}}

/* ---------- form controls, used by every form on the site ---------- */
.field{display:flex;flex-direction:column;gap:5px;min-width:0}
.field label{font-size:10.5px;letter-spacing:.13em;text-transform:uppercase;color:var(--muted);
  font-weight:600}
.field select,.field input,.field textarea{background:var(--surface-2);border:1px solid var(--line);
  border-radius:7px;padding:10px 11px;width:100%;color:var(--ink)}
.field select:focus,.field input:focus,.field textarea:focus{border-color:var(--navy-tint)}
/* ONE BASE, TWO SKINS. "The text height is different on the two buttons", 2026-11-17 —
   and it was, because the two rules each described their own box: 11px padding with no
   border against 10px padding with a 1px border, and NEITHER set a font-size or a
   line-height. Two buttons sitting side by side had no shared definition of how big
   their text was, so they agreed only by luck, and stopped agreeing as soon as one was
   a <button> (which inherits neither font-family nor font-size from the page) and the
   other an <a> (which inherits both).
   Now the metrics are declared once and the skins only change colour. Both carry the
   1px border — transparent on the solid one — so the two boxes are identical to the
   pixel rather than arithmetically equal by coincidence. */
.btn,.btn-ghost{display:inline-flex;align-items:center;justify-content:center;
  font-family:inherit;font-size:14.5px;line-height:1.25;font-weight:600;
  padding:12px 20px;border:1px solid transparent;border-radius:7px;
  cursor:pointer;text-decoration:none;white-space:nowrap}
.btn{background:var(--navy);color:#fff;border-color:var(--navy);align-self:end}
.btn:hover{background:var(--navy-tint);border-color:var(--navy-tint)}
.btn-ghost{background:transparent;color:var(--navy);border-color:var(--line)}
.btn-ghost:hover{background:var(--surface-2)}

/* ---------- search, answering as you choose ---------- */
.search-aside{display:flex;align-items:center;flex-wrap:wrap;gap:10px 16px;margin:16px 0 0}
.search-count{font-size:14px;color:var(--muted)}
.search-count b{color:var(--ink);font-weight:600;font-variant-numeric:tabular-nums}
.quick button{background:var(--surface);border:1px solid var(--line);border-radius:999px;
  padding:7px 13px;font-size:13px;color:var(--muted);cursor:pointer;
  transition:border-color .15s,color .15s,background .15s}
.quick button:hover{border-color:var(--navy);color:var(--navy);background:var(--surface)}

/* ---------- the agency ----------
   REBUILT 2026-11-17, on his own instruction and his own reference image:
   "remove the original information about MAURO on the right and insert an office
   photo instead ... style the overall layout as shown in Figure 2".

   WHAT WENT. The credentials panel that stood on the right. It had been laid over
   the office photograph on 16 Nov, and that is precisely what failed: four rows of
   type on top of a room made both harder to read than either alone. The photograph
   now gets the column to itself, uncovered.

   WHERE THE MATRICULA WENT. Nowhere -- it was never only here. The footer carries
   his name, his role and Col. 7103 L XIII F 88 on every page of the site, and
   /nosotros/, /contacto/ and /tasaciones/ each carry the full set of office rows.
   The proposal promises "tu ficha de martillero con nombre, matricula, direccion de
   la oficina y telefono" and it is still kept.

   WHAT THE REFERENCE CHANGES. In Figure 2 the band has no card: the text sits
   directly on the coloured field, with a rule leading into the eyebrow and the
   photograph framed rather than bled. So the white card goes, and `.sec--deep`
   finally does what its own comment always claimed -- "one inverted block, so the
   agency reads as a statement rather than a row". It was a white card on navy,
   which is the opposite of inverted. */
.agency{display:grid;grid-template-columns:1.06fr .94fr;gap:clamp(28px,5vw,64px);
  align-items:center;padding:clamp(18px,4vw,44px) 0}@container (max-width:900px) {.agency{grid-template-columns:1fr;gap:26px;padding:4px 0}}
.agency>*{min-width:0}
/* The rule that leads into the eyebrow, as in the reference. It is a real element
   of the band and not a border on the text, so it keeps its length when the words
   above it wrap. */
.agency .eyebrow{display:flex;align-items:center;gap:12px;color:var(--on-navy-dim)}
.agency .eyebrow::before{content:"";width:26px;height:2px;flex:none;border-radius:2px;
  background:var(--on-navy-dim);opacity:.8}
.agency h2{font-family:var(--serif);font-weight:400;font-size:clamp(28px,3.4vw,42px);
  line-height:1.12;letter-spacing:-.015em;color:var(--on-navy);margin:14px 0 0}
.agency p{font-family:var(--serif);font-size:16.5px;line-height:1.62;
  color:var(--on-navy-dim);margin:16px 0 0;max-width:54ch}
.agency p + p{margin-top:12px}
.agency-actions{display:flex;flex-wrap:wrap;gap:10px;margin-top:26px}
/* On navy the two buttons have to swap grounds: the navy fill would vanish into the
   field and the ghost border was drawn in --line, a warm grey meant for white. */
.agency-actions .btn{background:#fff;color:var(--navy);align-self:auto}
.agency-actions .btn:hover{background:var(--on-navy-dim);color:var(--navy-deep)}
.agency-actions .btn-ghost{color:#fff;border-color:rgba(255,255,255,.42)}
.agency-actions .btn-ghost:hover{background:rgba(255,255,255,.12);border-color:#fff}
/* Once the band is one column the two buttons stack, and two buttons of different
   widths stacked on a left edge read as a mistake rather than as a pair — their right
   edges land wherever the words happen to end. Stretched, they are one block with one
   edge, which is what a column of actions should look like. */
@container (max-width:760px) {
  .agency-actions{flex-direction:column;align-items:stretch;gap:9px}
  .agency-actions .btn,.agency-actions .btn-ghost{width:100%}}

/* His office, with nothing written across it. Framed the way the reference frames
   its photograph: a light hairline that reads as a frame against the navy, a radius
   larger than a card's, and a shadow deep enough to lift it off the field.
   `aspect-ratio` holds the shape before the file arrives, so the band does not jump
   as the page loads -- and the fallback ground is navy-deep, not white, because a
   white flash on a navy field is the most visible loading artefact there is. */
.agency-photo{margin:0;border-radius:18px;overflow:hidden;position:relative;
  border:1px solid rgba(255,255,255,.22);background:var(--navy-deep);
  box-shadow:0 34px 70px -34px rgba(0,3,36,.9)}
.agency-photo img{display:block;width:100%;height:100%;object-fit:cover;aspect-ratio:4/3}@container (max-width:900px) {.agency-photo img{aspect-ratio:16/10}}

/* ---------- reseñas ----------
   The reference he named carries client reviews and he singled them out. The
   section is built, but NOT filled: we hold no real review from a real client
   of his, and inventing one would be fabricating a testimonial. It shows him
   the shape and asks him for three real ones. */
/* ---------- what his clients said ----------
   Rebuilt 2026-11-17, when the band stopped being three dotted placeholders and
   became three real Google reviews. Placeholder styling was right for a space
   waiting to be filled and wrong for the only words on this site written by
   somebody other than him: of everything here, these are what a stranger
   weighing a martillero actually reads.

   So the band earns a field of its own, the cards sit on it rather than beside
   it, and each one is built around the person who wrote it — an initial, a
   name, a date, and the mark of where it came from. The quotation glyph is
   decorative and sits behind the text at low opacity; the stars appear only
   when a rating is known, which is why they are a separate row and not baked
   into the card. */
.sec--revs{background:var(--surface-2)}
.revs{display:grid;grid-template-columns:repeat(3,1fr);gap:18px}@container (max-width:900px) {.revs{grid-template-columns:1fr;gap:14px}}

.rev{position:relative;isolation:isolate;overflow:hidden;
  border:1px solid var(--line);border-radius:16px;padding:26px 24px 20px;
  background:var(--surface);display:flex;flex-direction:column;gap:14px;
  box-shadow:0 1px 2px rgba(20,22,31,.04);
  transition:transform .2s ease,box-shadow .2s ease,border-color .2s ease}
.rev:hover{transform:translateY(-3px);border-color:var(--navy-tint);
  box-shadow:0 18px 44px -26px rgba(1,7,79,.55)}

/* The opening quotation mark, large and almost invisible. It gives the card a
   centre of gravity without competing with the words. */
.rev::before{content:'“';position:absolute;top:-30px;right:14px;
  font-family:var(--serif);font-size:150px;line-height:1;color:var(--navy);
  opacity:.07;pointer-events:none;user-select:none}

.rev-stars{display:flex;gap:2px;color:#E8A317}
.rev p{margin:0;font-family:var(--serif);font-size:16.5px;line-height:1.58;
  color:var(--ink);flex:1}

/* The person, on a line of their own under a hairline. */
.rev-who{margin-top:auto;display:flex;align-items:center;gap:11px;
  padding-top:14px;border-top:1px solid var(--line-soft)}
.rev-avatar{flex:none;width:38px;height:38px;border-radius:50%;
  display:grid;place-items:center;font-family:var(--serif);font-size:17px;
  color:var(--on-navy);background:linear-gradient(135deg,var(--navy-tint),var(--navy))}
.rev-id{display:flex;flex-direction:column;gap:1px;min-width:0}
.rev-id b{font-size:14px;color:var(--ink);font-weight:600}
.rev-id span{font-size:12px;color:var(--muted)}
.rev-src{margin-left:auto;flex:none;display:inline-flex;align-items:center;gap:5px;
  font-size:11px;color:var(--muted);border:1px solid var(--line);
  border-radius:999px;padding:4px 9px;background:var(--surface-2)}
.rev-src svg{display:block}

/* The badge beside the heading: the same claim as the chip on each card, made
   once and in a place a visitor reads before the quotes themselves. */
.rev-badge{display:inline-flex;align-items:center;gap:7px;text-decoration:none;
  font-size:12.5px;color:var(--muted);background:var(--surface);
  border:1px solid var(--line);border-radius:999px;padding:7px 14px;
  transition:border-color .18s,color .18s}
.rev-badge:hover{border-color:var(--navy-tint);color:var(--navy)}

/* ---------- flowing ----------
   The reference he chose moves as you go down it rather than snapping into
   place. One transition does most of that work: content rises a little as it
   comes into view. It is deliberately small — 14 px and 0.7 s — because the
   point is that the page feels unhurried, not that it performs. */
.reveal{opacity:0;transform:translateY(14px);
  transition:opacity .7s cubic-bezier(.22,.61,.36,1),transform .7s cubic-bezier(.22,.61,.36,1)}
.reveal.in{opacity:1;transform:none}@media (prefers-reduced-motion:reduce) {
  .reveal{opacity:1!important;transform:none!important;transition:none}}

/* ---------- 2 · what are you looking for ----------
   Photographic tiles rather than outline icons. Every other block on this page
   is carried by a picture, and eight little glyphs on white read as a form, not
   as a way in. Each tile is lit by his own sharpest photograph of that type, so
   the section is also a second look at the stock. The counts are real: a
   shortcut that promises eight and returns two is worse than no shortcut. */
/* ---------- 2 · the two shortcut bands ----------
   REBUILT A THIRD TIME, 2026-11-17, and this time the right thing changed.

   His words: "Doesn't it feel like Figures 1 and 2 are identical in every aspect — to
   the point where you can't tell what section they are trying to show — except for the
   pictures and text?" He was right, and the two previous passes had both missed it. I
   changed headings and the order of two lines; the ANATOMY stayed identical — a
   photograph on top, a white body under it, a link at the foot, eight of one and three
   of the other. Two sections built from the same object read as one section, whatever
   the headings say.

   So they are now two different objects, and they say different things:

   TYPES ARE A MENU. Eight categories, and the photograph was never able to carry one:
   the Local tile was a cadastral plan, Lote a length of wall, Oficina a grey doorway.
   Photographs are gone from this band. What is left is a large glyph on a tinted
   ground, the name, and the count — dense, four across, obviously a set of filters
   rather than a set of listings.

   ZONES ARE PLACES. Three of them, and here a photograph IS the subject: it shows what
   the locality looks like. So they keep the picture, go full-bleed, and carry the name
   over the image with a map pin — the shape every map and travel site uses for a
   place, which is exactly what these are.

   Different anatomy, different density, different text placement. No one has to read a
   heading to tell them apart. */

/* ---------- 2 · what are you looking for ----------
   Photographic tiles rather than outline icons. Every other block on this page
   is carried by a picture, and eight little glyphs on white read as a form, not
   as a way in. Each tile is lit by his own sharpest photograph of that type, so
   the section is also a second look at the stock. The counts are real: a
   shortcut that promises eight and returns two is worse than no shortcut. */
.shortcuts{display:grid;grid-template-columns:repeat(4,1fr);gap:14px}@container (max-width:1000px) {.shortcuts{grid-template-columns:repeat(3,1fr)}}@container (max-width:760px) {.shortcuts{grid-template-columns:repeat(2,1fr)}}
.shortcut{position:relative;overflow:hidden;border:0;padding:0;cursor:pointer;
  border-radius:var(--radius);aspect-ratio:5/4;display:flex;align-items:flex-end;
  isolation:isolate;background:var(--surface-2);text-align:left;
  transition:transform .18s cubic-bezier(.22,.61,.36,1),box-shadow .18s}@container (max-width:760px) {.shortcut{aspect-ratio:4/3}}
.shortcut:hover{transform:translateY(-3px);box-shadow:0 18px 38px -18px rgba(20,22,31,.5)}
.shortcut img{position:absolute;inset:0;width:100%;height:100%;object-fit:cover;z-index:0;
  transition:transform .9s cubic-bezier(.22,.61,.36,1)}
.shortcut:hover img{transform:scale(1.07)}
.shortcut::after{content:"";position:absolute;inset:0;z-index:1;
  background:linear-gradient(to top,rgba(6,8,16,.92) 0%,rgba(6,8,16,.55) 42%,
    rgba(6,8,16,.12) 72%,rgba(6,8,16,.06) 100%)}
.sc-in{position:relative;z-index:2;padding:14px 15px;display:flex;flex-direction:column;gap:2px}
.sc-in b{font-size:16.5px;font-weight:600;color:#fff;letter-spacing:-.005em}
.sc-in span{font-size:12.5px;color:rgba(255,255,255,.88);font-variant-numeric:tabular-nums}
.sc-go{position:absolute;right:12px;bottom:12px;z-index:2;width:30px;height:30px;
  border-radius:50%;background:rgba(255,255,255,.16);display:grid;place-items:center;
  color:#fff;transition:background .18s}
.shortcut:hover .sc-go{background:rgba(255,255,255,.3)}@media (prefers-reduced-motion:reduce) {
  .shortcut,.shortcut img{transition:none}
  .shortcut:hover{transform:none}.shortcut:hover img{transform:none}}

/* a compact segmented control for the featured tabs */
.ops-sm{margin-left:auto;padding:3px;align-self:center}
.ops-sm button{padding:7px 14px;font-size:13px;white-space:nowrap}

/* ---------- 2b · zones: places, with the place in the picture ---------- */
.zones{display:grid;grid-template-columns:repeat(3,1fr);gap:18px}@container (max-width:860px) {.zones{grid-template-columns:1fr;gap:14px}}

/* ---------- the zone map ----------
   "There is a map, and three points appear alongside place names, appearing as if they
   are protruding far to the right from their corresponding locations on the map."
   2026-11-17, replacing the photograph he rejected on sight.

   THE GEOMETRY IS ONE FLEX LINE PER PLACE. Each row spans the whole band: a spacer
   whose width is the dot's own x position, then the dot, then a line that takes
   whatever is left, then the label. That is why the template only has to emit two
   numbers per locality -- a top and a width -- and never has to know how wide a label
   is or where the map ends. Absolutely positioning four separate pieces and keeping
   them in line would have needed all of that. */
.zonemap{position:relative;border-radius:18px;overflow:hidden;margin:0 0 18px;
  background:var(--surface-2);border:1px solid var(--line-soft);aspect-ratio:16/9}
/* NO aspect override at any width: the container has to keep the image shape, or
   object-fit crops the map and every dot drifts from the place it names. */

/* The map is the ground, not the subject: desaturated and dimmed so the dots, the
   lines and the labels are what the eye lands on. */
.zonemap-img{position:absolute;inset:0;width:100%;height:100%;object-fit:cover;
  filter:saturate(.45) contrast(.95) brightness(1.03);opacity:.85}

/* The question, set large and low-contrast across the field -- it reads as part of the
   map rather than as a caption sitting on top of it. */
/* ONE QUESTION MARK, not four. There were three on the rows and another inside this
   sentence; he asked for a single one, arranged well. So the rows carry none and the
   mark here is the composition: an outsized glyph with the question set against it,
   low enough in contrast to stay part of the map rather than sit on top of it. */
.zonemap-ask{position:absolute;left:4%;bottom:6%;margin:0;z-index:1;
  display:flex;align-items:center;gap:14px;pointer-events:none;max-width:46%}
.zonemap-ask span{font-family:var(--serif);font-size:clamp(58px,8vw,104px);
  line-height:.78;color:var(--navy);opacity:.17;font-style:italic}
.zonemap-ask b{font-family:var(--serif);font-weight:400;
  font-size:clamp(15px,1.9vw,22px);line-height:1.2;color:var(--navy);opacity:.55}

/* THE DOT MARKS THE PLACE; THE LABEL IS FREE TO MOVE.

   La Plata and Bavio are 7% apart on this map and the labels are taller than that, so
   they overlapped -- 2026-11-17. Spreading the DOTS would be lying about where the
   towns are, so the dots stay put, the labels are pushed clear in PHP, and a line is
   drawn between the two. Which is what a paper map does when two towns sit close
   together. */
.zm-links{position:absolute;inset:0;width:100%;height:100%;z-index:1;
  pointer-events:none;overflow:visible}
.zm-links line{stroke:var(--navy);stroke-width:1.5;opacity:.45;stroke-linecap:round}

/* A dot with a halo, so it holds against whatever the map happens to be underneath.
   Translated by half its own size, so `left`/`top` are the true position of the place
   rather than the corner of a box. */
.zm-dot{position:absolute;z-index:2;width:17px;height:17px;border-radius:50%;
  display:grid;place-items:center;background:rgba(255,255,255,.96);
  transform:translate(-50%,-50%);pointer-events:none;
  box-shadow:0 2px 9px rgba(20,22,31,.35)}
.zm-dot i{width:7px;height:7px;border-radius:50%;background:var(--navy);display:block}

.zm-label{position:absolute;z-index:3;display:flex;flex-direction:column;gap:1px;
  transform:translateY(-50%);text-decoration:none;
  background:rgba(255,255,255,.97);border:1px solid var(--line-soft);
  -webkit-backdrop-filter:blur(6px);backdrop-filter:blur(6px);
  border-radius:11px;padding:8px 12px;
  box-shadow:0 10px 24px -14px rgba(20,22,31,.5);
  transition:box-shadow .2s,border-color .2s,transform .2s cubic-bezier(.22,.61,.36,1)}
/* Near the right edge the label hangs the other way, so it cannot run off the map. */
.zm-label--flip{transform:translate(-100%,-50%)}
.zm-label:hover{border-color:var(--navy-tint);
  box-shadow:0 16px 32px -14px rgba(20,22,31,.62);
  transform:translateY(-50%) scale(1.04)}
.zm-label--flip:hover{transform:translate(-100%,-50%) scale(1.04)}
.zm-label b{font-size:14.5px;font-weight:600;color:var(--ink);letter-spacing:-.01em;
  line-height:1.2;white-space:nowrap}
.zm-label span{font-size:12px;color:var(--muted);font-variant-numeric:tabular-nums;
  white-space:nowrap}

/* On a narrow screen the map is the same shape but far smaller, so the labels have to
   come down with it or three of them fill the frame. */
/* On a narrow screen the map is the same shape but far smaller, so the labels have to
   come down with it — and harder than they used to, because three of them have to fit
   inside a band only a couple of hundred pixels tall. */
@container (max-width:700px) {
  .zm-label{padding:5px 8px;border-radius:8px;gap:0}
  .zm-label b{font-size:11.5px}
  .zm-label span{font-size:9.5px}
  .zm-dot{width:13px;height:13px}
  .zm-dot i{width:5px;height:5px}
  .zonemap-ask{max-width:52%}}

.zonemap-credit{position:absolute;right:8px;bottom:5px;margin:0;z-index:2;
  font-size:10px;color:var(--muted);opacity:.75;pointer-events:none}

/* Reduced motion, for the map. The blocks that used to sit here also styled .zm-q and
   .zm-row -- neither of which exists any more -- and ended in a declaration with no
   selector. That orphan is what broke the home page on 2026-11-17: its stray closing
   brace put the parser into an error state and the next rule, `.zone`, was discarded,
   so the zone cards lost their height and all three captions stacked in one place. */
@media (prefers-reduced-motion:reduce) {
  .zm-dot,.zm-label{transition:none}
  .zm-label:hover{transform:translateY(-50%)}
  .zm-label--flip:hover{transform:translate(-100%,-50%)}}

.zone{position:relative;display:block;overflow:hidden;border-radius:16px;border:0;
  padding:0;cursor:pointer;text-align:left;text-decoration:none;isolation:isolate;
  aspect-ratio:4/3;background:var(--surface-2);
  transition:transform .2s cubic-bezier(.22,.61,.36,1),box-shadow .2s}@container (max-width:860px) {.zone{aspect-ratio:16/9}}
.zone:hover{transform:translateY(-4px);box-shadow:0 26px 50px -24px rgba(20,22,31,.6)}
.zone:focus-visible{outline:2px solid var(--navy);outline-offset:3px}

.zone-shot{position:absolute;inset:0;z-index:0}
.zone-shot img{width:100%;height:100%;object-fit:cover;
  transition:transform .9s cubic-bezier(.22,.61,.36,1)}
.zone:hover .zone-shot img{transform:scale(1.07)}

/* Deep enough at the foot to carry white type over any photograph he has, and clear at
   the top so the locality is still visible. */
.zone::after{content:"";position:absolute;inset:0;z-index:1;
  background:linear-gradient(to top,rgba(6,8,16,.88) 0%,rgba(6,8,16,.5) 38%,
    rgba(6,8,16,.08) 70%,rgba(6,8,16,0) 100%)}

.zone-in{position:absolute;z-index:2;left:0;right:0;bottom:0;
  display:flex;flex-direction:column;gap:3px;padding:16px 18px 16px}
.zone-name{display:flex;align-items:center;gap:8px}
.zone-name svg{flex:none;color:#fff;opacity:.9}
.zone-in b{font-size:21px;font-weight:600;color:#fff;letter-spacing:-.01em;
  text-shadow:0 1px 12px rgba(0,0,0,.5)}
.zone-kicker{font-size:13px;color:rgba(255,255,255,.9);font-variant-numeric:tabular-nums;
  text-shadow:0 1px 10px rgba(0,0,0,.5)}

/* A count chip in the opposite corner from the name, so the card has two anchors and
   reads as a place card rather than a photograph with a caption. */
.zone-go{position:absolute;z-index:2;top:12px;right:12px;display:inline-flex;
  align-items:center;gap:6px;padding:7px 11px;border-radius:999px;font-size:12.5px;
  font-weight:600;color:#fff;background:rgba(10,12,20,.42);
  border:1px solid rgba(255,255,255,.26);
  -webkit-backdrop-filter:blur(7px);backdrop-filter:blur(7px);
  transition:background .18s,transform .18s cubic-bezier(.22,.61,.36,1)}
.zone:hover .zone-go{background:rgba(10,12,20,.62);transform:translateX(2px)}
.zone-go svg{flex:none}@media (prefers-reduced-motion:reduce) {
  .zone,.zone-shot img,.zone-go{transition:none}
  .shortcut:hover,.zone:hover{transform:none}
  .zone:hover .zone-shot img{transform:none}
  .shortcut:hover .sc-go{transform:none}}

/* a compact segmented control for the featured tabs */
.ops-sm{margin-left:auto;padding:3px;align-self:center}
.ops-sm button{padding:7px 14px;font-size:13px;white-space:nowrap}


/* ---------- rotating shelves ----------
   "Que se vean solo dos y que vayan cambiando automáticas … para que no sea
   tan larga la página." Two at a time instead of six, moving on their own, so
   the same stock takes a third of the height.

   It is a scroll container rather than a transformed track: that gives native
   swiping on a phone and keyboard scrolling for free, and the browser does the
   snapping. Autoplay is just a scroll, so a human grabbing it mid-slide never
   fights the animation. */
.shelf{position:relative}
.shelf-track{display:flex;gap:18px;overflow-x:auto;scroll-snap-type:x mandatory;
  scrollbar-width:none;-ms-overflow-style:none;padding:4px 2px;margin:-4px -2px}
.shelf-track::-webkit-scrollbar{display:none}
.shelf-track > .card{flex:0 0 calc((100% - 18px) / 2);scroll-snap-align:start}@container (max-width:760px) {
  .shelf-track{gap:14px}
  .shelf-track > .card{flex:0 0 100%}}
.shelf-foot{display:flex;align-items:center;gap:12px;margin-top:16px}
.shelf-dots{display:flex;gap:6px}
.shelf-dots button{width:7px;height:7px;padding:0;border-radius:50%;border:0;cursor:pointer;
  background:var(--line);transition:background .2s,width .2s}
.shelf-dots button[aria-current="true"]{background:var(--navy);width:22px;border-radius:4px}
.shelf-arrows{margin-left:auto;display:flex;gap:8px}
.shelf-arrows button{width:36px;height:36px;border-radius:50%;cursor:pointer;
  border:1px solid var(--line);background:var(--surface);color:var(--navy);
  display:grid;place-items:center;transition:border-color .15s,background .15s}
.shelf-arrows button:hover{border-color:var(--navy);background:var(--surface-2)}

/* ---------- the three paths ----------
   A visitor is one of three people, and the page should not make them work out
   which. Buy and rent go straight into a filtered catalogue; the third goes to
   the valuation, which is the only reason an owner is here. */
.paths{display:grid;grid-template-columns:repeat(3,auto);gap:12px;margin:0;
  justify-content:start;width:auto}@container (max-width:860px) {.paths{justify-content:center}}@container (max-width:620px) {.paths{grid-template-columns:1fr;gap:9px;width:100%}}
/* The three ways in. BOTH selectors, deliberately: the mockup draws them as
   <button> and the live theme ships <a href> — real links, crawlable and
   middle-clickable, which is the better choice. On 2026-11-14 he reported
   "faltan los 3 botones": the markup was there and `.paths button` matched none
   of it, so only the text rules applied and the pills never appeared. */
.paths a,.paths button{display:flex;flex-direction:column;align-items:flex-start;gap:2px;cursor:pointer;
  text-decoration:none;
  background:rgba(10,12,20,.44);border:1px solid rgba(255,255,255,.55);border-radius:10px;
  padding:13px 22px;backdrop-filter:blur(6px);-webkit-backdrop-filter:blur(6px);
  transition:background .18s,border-color .18s,transform .18s}
.paths a:hover,.paths button:hover{background:rgba(255,255,255,.96);border-color:#fff;transform:translateY(-2px)}
.paths b{font-size:16px;font-weight:600;color:#fff}
.paths span{font-size:12.5px;color:rgba(255,255,255,.88)}
.paths a:hover b,.paths button:hover b{color:var(--navy)}
.paths a:hover span,.paths button:hover span{color:var(--muted)}@container (max-width:620px) {.paths a,.paths button{align-items:center}}@media (prefers-reduced-motion:reduce) {.paths a,.paths button{transition:none}
  .paths button:hover{transform:none}}

/* the code lookup lives beside the search now, not in a card of its own */
.codefind{display:flex;align-items:center;gap:8px;margin-left:auto}@container (max-width:760px) {.codefind{margin-left:0;width:100%}}
.codefind label{font-size:12.5px;color:var(--muted);white-space:nowrap}
.codefind input{width:110px;flex:0 1 auto;min-width:0;background:var(--surface);
  border:1px solid var(--line);border-radius:7px;padding:8px 10px;color:var(--ink);
  font-weight:600;letter-spacing:.06em;text-transform:uppercase}
.codefind input::placeholder{font-weight:400;letter-spacing:0;color:var(--muted);
  text-transform:none}
.codefind .btn-ghost{padding:8px 14px}
.code-msg{margin:8px 0 0;font-size:13px;color:var(--warn);min-height:0}
.code-msg:empty{display:none}
.quick{display:flex;flex-wrap:wrap;gap:7px;margin:14px 0 0}

/* the owner's four steps */
.steps{list-style:none;counter-reset:s;margin:18px 0 6px;padding:0;display:grid;gap:10px}
.steps li{counter-increment:s;display:flex;flex-direction:column;gap:1px;padding-left:34px;
  position:relative}
.steps li::before{content:counter(s);position:absolute;left:0;top:1px;width:23px;height:23px;
  border-radius:50%;background:var(--navy);color:#fff;font-size:12px;font-weight:600;
  display:grid;place-items:center}
.steps b{font-size:14.5px;color:var(--ink)}
.steps span{font-size:13.5px;color:var(--muted);line-height:1.45}

/* the closing invitation */
.closing{display:flex;align-items:center;gap:28px;flex-wrap:wrap;
  background:var(--surface);border:1px solid var(--line);border-radius:var(--radius);
  padding:32px 34px}@container (max-width:760px) {.closing{padding:22px 20px;gap:18px}}
.closing h2{font-family:var(--serif);font-weight:400;font-size:28px;line-height:1.16;
  letter-spacing:-.015em;color:var(--navy);margin:0;max-width:22ch}
.closing p{margin:8px 0 0;font-size:15.5px;line-height:1.55;color:var(--muted);max-width:52ch}
.closing-actions{margin-left:auto;display:flex;gap:10px;flex-wrap:wrap}@container (max-width:760px) {.closing-actions{margin-left:0}}

/* ---------- property cards ---------- */
.grid{display:grid;gap:18px;grid-template-columns:repeat(3,1fr)}@container (max-width:980px) {.grid{grid-template-columns:repeat(2,1fr)}}@container (max-width:620px) {.grid{grid-template-columns:1fr;gap:14px}}
.card{text-decoration:none;color:inherit;display:flex;flex-direction:column;background:var(--surface);border:1px solid var(--line);
  border-radius:var(--radius);overflow:hidden;cursor:pointer;text-align:left;padding:0;
  transition:border-color .15s,transform .15s,box-shadow .15s}
.card:hover{border-color:var(--navy-tint);transform:translateY(-2px);box-shadow:var(--shadow)}
.card:focus-visible{outline:2px solid var(--navy-tint);outline-offset:2px}
.card-img{position:relative;aspect-ratio:4/3;background:var(--surface-2);overflow:hidden}
.card-img img{width:100%;height:100%;object-fit:cover;
  transition:transform .8s cubic-bezier(.22,.61,.36,1)}

/* ---------- flipping through a card's photographs ----------
   Without this you have to open a property to find out whether its other
   photographs are any better, which is a lot of clicking on a catalogue where
   the lead photograph is often the weakest one he has. The arrows sit inside
   the image and never trigger the card itself. */
.card-nav{position:absolute;top:50%;transform:translateY(-50%);z-index:3;
  width:34px;height:34px;border:0;border-radius:50%;cursor:pointer;
  background:rgba(8,10,18,.52);color:#fff;display:grid;place-items:center;
  opacity:0;transition:opacity .18s,background .18s}
.card-nav.prev{left:8px}
.card-nav.next{right:8px}
.card:hover .card-nav,.card:focus-within .card-nav{opacity:1}
.card-nav:hover{background:rgba(8,10,18,.78)}
.card-nav:focus-visible{opacity:1}
/* on a touch screen there is no hover, so they stay visible */
@media (hover:none) {.card-nav{opacity:1}}
.card-count{position:absolute;left:10px;bottom:10px;z-index:3;font-size:11px;
  padding:3px 8px;border-radius:5px;background:rgba(0,0,0,.55);color:#fff;
  font-variant-numeric:tabular-nums;opacity:0;transition:opacity .18s}
.card:hover .card-count,.card:focus-within .card-count{opacity:1}@media (hover:none) {.card-count{opacity:1}}
.card:hover .card-img img{transform:scale(1.06)}@media (prefers-reduced-motion:reduce) {.card-img img{transition:none}
  .card:hover .card-img img{transform:none}}
.badge{position:absolute;left:10px;top:10px;font-size:11px;font-weight:600;letter-spacing:.06em;
  text-transform:uppercase;padding:4px 9px;border-radius:5px;background:var(--navy);color:#fff}
.badge.alq{background:var(--alquiler)}
.codigo{position:absolute;right:10px;top:10px;font-size:11px;font-weight:600;padding:4px 8px;
  border-radius:5px;background:rgba(0,0,0,.55);color:#fff;letter-spacing:.04em}
.shots{position:absolute;right:10px;bottom:10px;font-size:11px;padding:3px 8px;border-radius:5px;
  background:rgba(0,0,0,.55);color:#fff;font-variant-numeric:tabular-nums}
.card-body{padding:14px;display:flex;flex-direction:column;gap:8px;flex:1}
.price{font-size:19px;font-weight:600;letter-spacing:-.01em;font-variant-numeric:tabular-nums}
.price small{font-size:12px;font-weight:500;color:var(--muted);letter-spacing:.04em}
.card h3{font-size:15px;font-weight:600;line-height:1.35}
.addr{font-size:13.5px;color:var(--muted);line-height:1.4}
.chips{display:flex;flex-wrap:wrap;gap:6px;margin-top:auto;padding-top:4px}
.chip{font-size:11.5px;border:1px solid var(--line);border-radius:5px;padding:3px 8px;color:var(--muted)}
.chip.t{border-color:var(--line-soft);background:var(--surface-2);color:var(--ink);font-weight:500}
.specs{display:flex;flex-wrap:wrap;gap:10px 14px;font-size:13px;color:var(--muted);
  font-variant-numeric:tabular-nums}
.specs i{font-style:normal;color:var(--ink);font-weight:600}

/* ---------- the owner's band ----------
   A split panel: the offer on the left, a photograph with the mark on it on the
   right. It replaces the solid navy block that said the same thing, because a
   flat colour band is the one shape on this page that looks like a template.
   The photograph is a hand passing keys, deliberately not a stock "agent": a
   model presented as the agency would imply staff he does not have. */
.pitch{display:grid;grid-template-columns:1fr 1fr;gap:0;border-radius:var(--radius);
  overflow:hidden;border:1px solid var(--line);background:var(--surface-2)}@container (max-width:860px) {.pitch{grid-template-columns:1fr}}
.pitch-copy{padding:48px 46px;display:flex;flex-direction:column;align-items:flex-start;
  justify-content:center;gap:14px}@container (max-width:860px) {.pitch-copy{padding:28px 22px}}
/* 18ch forced "¿Tenés una / propiedad para / vender o alquilar?" into three
   stubby lines in a column that had room for two. Width first, then size. */
.pitch-copy h2{font-family:var(--serif);font-weight:400;font-size:33px;line-height:1.16;
  letter-spacing:-.015em;color:var(--navy);margin:0;max-width:24ch;text-wrap:balance}@container (max-width:1100px) {.pitch-copy h2{font-size:29px}}@container (max-width:860px) {.pitch-copy h2{font-size:26px;max-width:22ch}}
.pitch-copy p{margin:0;font-size:16px;line-height:1.6;color:var(--muted);max-width:46ch}
.pitch-copy .btn-ghost{margin-top:8px;background:var(--surface)}
.pitch-art{position:relative;min-height:330px;overflow:hidden;isolation:isolate}@container (max-width:860px) {.pitch-art{min-height:240px}}
.pitch-art img.shot-img{position:absolute;inset:0;width:100%;height:100%;object-fit:cover;z-index:0}
.pitch-art::after{content:"";position:absolute;inset:0;z-index:1;
  background:linear-gradient(to right,rgba(6,8,16,.62) 0%,rgba(6,8,16,.30) 52%,
    rgba(6,8,16,.42) 100%)}
.pitch-mark{position:relative;z-index:2;height:100%;display:flex;flex-direction:column;
  align-items:flex-start;justify-content:center;gap:10px;padding:0 42px}@container (max-width:860px) {.pitch-mark{padding:0 22px}}
.pitch-mark img{height:62px;width:auto;filter:drop-shadow(0 6px 20px rgba(0,0,0,.45))}@container (max-width:860px) {.pitch-mark img{height:46px}}
.pitch-mark span{font-size:12px;letter-spacing:.24em;text-transform:uppercase;
  font-weight:600;color:#fff;background:rgba(6,8,16,.34);padding:6px 12px;border-radius:999px}

/* ---------- results screen ---------- */
.results>*{min-width:0}
.results{display:grid;grid-template-columns:238px 1fr;gap:26px;align-items:start}@container (max-width:900px) {.results{grid-template-columns:1fr}}
.filters{background:var(--surface-2);border:1px solid var(--line);border-radius:var(--radius);
  padding:16px;display:flex;flex-direction:column;gap:14px;position:sticky;top:calc(var(--head-stuck) + 14px)}@container (max-width:900px) {.filters{position:static}}
.filters h3{font-size:12px;letter-spacing:.14em;text-transform:uppercase;color:var(--muted)}
.ops{display:flex;background:var(--surface);border:1px solid var(--line);border-radius:7px;padding:3px}
.ops button{flex:1;background:none;border:0;padding:7px 4px;border-radius:5px;cursor:pointer;
  font-size:13px;font-weight:500;color:var(--muted)}
.ops button[aria-pressed="true"]{background:var(--navy);color:#fff;font-weight:600}
.checks{display:flex;flex-direction:column;gap:7px;max-height:none}
.checks label{display:flex;align-items:center;gap:8px;font-size:14px;cursor:pointer}
.checks input{accent-color:var(--navy);width:15px;height:15px;margin:0}
.checks em{margin-left:auto;font-style:normal;font-size:12px;color:var(--muted);
  font-variant-numeric:tabular-nums}
.rhead{display:flex;align-items:center;gap:12px;flex-wrap:wrap;margin-bottom:16px}
.rhead p{margin:0;font-size:14px;color:var(--muted)}
.rhead p b{color:var(--ink);font-weight:600}
.rhead select{margin-left:auto;background:var(--surface);border:1px solid var(--line);
  border-radius:7px;padding:8px 10px}
.empty{border:1px dashed var(--line);border-radius:var(--radius);padding:30px;text-align:center;
  color:var(--muted)}

/* ---------- property detail ---------- */
.ficha>*{min-width:0}
.ficha{display:grid;grid-template-columns:1fr 316px;gap:28px;align-items:start}@container (max-width:900px) {.ficha{grid-template-columns:1fr;gap:22px}}
.gallery{display:flex;flex-direction:column;gap:8px}
.gmain{aspect-ratio:3/2;border-radius:var(--radius);overflow:hidden;background:var(--surface-2);
  position:relative}
.gmain img{width:100%;height:100%;object-fit:cover}
.gthumbs{display:flex;gap:8px;overflow-x:auto;padding-bottom:4px}
.gthumbs button{flex:none;width:84px;aspect-ratio:4/3;border-radius:7px;overflow:hidden;padding:0;
  border:2px solid transparent;background:none;cursor:pointer}
.gthumbs button[aria-current="true"]{border-color:var(--navy-tint)}
.gthumbs img{width:100%;height:100%;object-fit:cover}
.ficha-head{display:flex;flex-direction:column;gap:10px;margin:22px 0 0}
.ficha-head .price{font-size:28px}
.block{border-top:1px solid var(--line-soft);padding:22px 0 0;margin-top:22px;
  display:flex;flex-direction:column;gap:12px}
.block h2{font-size:17px}
.desc{font-family:var(--serif);font-size:16.5px;line-height:1.65;max-width:66ch;white-space:pre-line}
.dl{display:grid;grid-template-columns:repeat(auto-fit,minmax(130px,1fr));gap:1px;
  background:var(--line-soft);border:1px solid var(--line-soft);border-radius:var(--radius);
  overflow:hidden}
.dl div{background:var(--surface);padding:12px 14px}
.dl dt{font-size:11px;letter-spacing:.12em;text-transform:uppercase;color:var(--muted);font-weight:600}
.dl dd{margin:3px 0 0;font-size:16px;font-weight:600;font-variant-numeric:tabular-nums}

/* map: hand-drawn grid, because 24 of the 29 listings have no coordinates yet */
.map{aspect-ratio:16/9;border:1px solid var(--line);border-radius:var(--radius);position:relative;
  overflow:hidden;background:var(--surface-2)}
.map::before{content:"";position:absolute;inset:0;background:
   repeating-linear-gradient(0deg,var(--line-soft) 0 1px,transparent 1px 38px),
   repeating-linear-gradient(90deg,var(--line-soft) 0 1px,transparent 1px 38px),
   linear-gradient(45deg,transparent calc(50% - 1px),var(--line) 50%,transparent calc(50% + 1px))}
.pin{position:absolute;left:50%;top:50%;width:16px;height:16px;border-radius:50%;
  background:var(--navy);border:3px solid var(--surface);transform:translate(-50%,-50%);
  box-shadow:0 0 0 7px color-mix(in srgb,var(--navy) 18%,transparent)}
.map figcaption{position:absolute;left:0;right:0;bottom:0;background:var(--surface);
  border-top:1px solid var(--line-soft);padding:9px 12px;font-size:12.5px;color:var(--muted)}

.aside{display:flex;flex-direction:column;gap:14px;position:sticky;top:calc(var(--head-stuck) + 14px)}@container (max-width:900px) {.aside{position:static}}
.panel{border:1px solid var(--line);border-radius:var(--radius);background:var(--surface-2);
  padding:16px;display:flex;flex-direction:column;gap:12px}
.agent{display:flex;gap:12px;align-items:center}
.avatar{width:46px;height:46px;border-radius:50%;background:var(--navy);color:#fff;flex:none;
  display:grid;place-items:center;font-weight:600;letter-spacing:.02em}
.agent b{display:block;font-size:15px}
.agent span{font-size:12.5px;color:var(--muted);line-height:1.35;display:block}
.form{display:flex;flex-direction:column;gap:10px}
.form textarea{min-height:84px;resize:vertical}
.wa{display:flex;align-items:center;justify-content:center;gap:8px;background:var(--surface);
  color:var(--alquiler);border:1.5px solid var(--alquiler);border-radius:7px;padding:10px 14px;
  font-weight:600;cursor:pointer}
.wa:hover{background:var(--alquiler);color:#fff}
.small{font-size:12px;color:var(--muted)}
.opt{font-weight:400;letter-spacing:0;text-transform:none;color:var(--muted);opacity:.8}

/* ---------- contact screen ---------- */

/* ---------- the institutional lede ----------
   "El texto esta corrido a la izquierda" -- 2026-11-17, with an arrow at the empty
   right half of Nosotros. He was right, and the cause was not a stray alignment:
   `.lede` carries a 60ch measure, which is correct for reading and wrong inside a
   1256px column, so the words filled 626px of it while the heading rule, the
   photograph and the contact grid below all ran on to the right edge past them.

   The measure stays -- 1256px lines are near 150 characters, which is harder to read,
   not easier -- and the COLUMN comes in to meet the text instead. On Nosotros the
   office photograph moves up beside the paragraphs and fills the space that was
   empty; on Contacto and Tasaciones, which have no photograph, the block is centred
   rather than left-hugging. Same measure, no void either way. */
.inst-lead{display:grid;gap:34px;align-items:start;
  border-top:1px solid var(--line-soft);padding-top:22px;margin:22px 0 26px}
.inst-lead>*{min-width:0}
.inst-text{display:flex;flex-direction:column;gap:12px}
.inst-text .lede{max-width:none}
.inst-lead.is-solo .inst-text{max-width:74ch;margin-left:auto;margin-right:auto}
.inst-lead.has-photo{grid-template-columns:minmax(0,1.04fr) minmax(0,.96fr)}
.inst-photo{margin:0;padding:0;border-radius:var(--radius);overflow:hidden;
  border:1px solid var(--line-soft);background:var(--surface-2)}
.inst-photo img{display:block;width:100%;height:auto}
/* Below 900px the photograph goes under the text rather than beside it: at half of
   a phone width it would be a thumbnail of his own office. */
@container (max-width:900px) {.inst-lead.has-photo{grid-template-columns:1fr;gap:22px}}
.contact>*{min-width:0}
.contact{display:grid;grid-template-columns:1fr 1fr;gap:28px;align-items:start}@container (max-width:860px) {.contact{grid-template-columns:1fr;gap:20px}}
.office{display:flex;flex-direction:column;gap:16px}
.office-row{display:flex;gap:12px;align-items:flex-start}
.office-row svg{flex:none;margin-top:2px;color:var(--navy-tint)}
.office-row b{display:block;font-size:11px;letter-spacing:.13em;text-transform:uppercase;
  color:var(--muted);font-weight:600;margin-bottom:2px}
.two{display:grid;grid-template-columns:1fr 1fr;gap:10px}@container (max-width:620px) {.two{grid-template-columns:1fr}}

/* ---------- footer ---------- */
/* Brand navy, not the deeper shade: the logo artwork carries its own navy
   rectangle, and on navy-deep that rectangle showed as a lighter box. */
.site-foot{background:var(--navy);color:var(--on-navy-dim);margin-top:10px}
.foot-in{max-width:1320px;margin:0 auto;padding:34px 32px;display:grid;
  grid-template-columns:1.4fr repeat(4,1fr);gap:26px}@container (max-width:1000px) {.foot-in{grid-template-columns:1fr 1fr 1fr}}
/* On a phone the five columns become one, and left-aligning all of it left the
   footer looking lopsided — the client's words on 2026-11-14: "the writings are
   biased to one side". Centred, it reads as a deliberate end to the page rather
   than a column that ran out of room. */
@container (max-width:760px) {
  .foot-in{grid-template-columns:1fr;gap:22px;padding:26px 16px;text-align:center}
  .foot-in .logo{margin-left:auto;margin-right:auto}
  .site-foot a{display:inline-block}
  .legal{text-align:center;padding:14px 16px}}
.site-foot h4{margin:0 0 10px;font-size:11px;letter-spacing:.14em;text-transform:uppercase;
  color:var(--on-navy);font-weight:600}
.site-foot a{display:block;color:var(--on-navy-dim);text-decoration:none;font-size:14px;
  padding:3px 0}
.site-foot a:hover{color:var(--on-navy)}
.site-foot p{margin:0;font-size:13px;line-height:1.55}
.legal{border-top:1px solid rgba(255,255,255,.12);padding:14px 32px;font-size:12px;
  max-width:1320px;margin:0 auto;color:var(--on-navy-dim)}

/* data the client still has to give us, marked rather than invented */
.tbc{border-bottom:1px dotted currentColor;opacity:.75;cursor:help}

/* ============================================================================
 * Additions — the parts of a real site the prototype never needed.
 *
 * This file is appended to the generated stylesheet by tools/build_theme_css.py, so
 * the served CSS is still one file, and the approved mockup above is still the only
 * source of the approved design. Nothing here restyles anything he signed off: every
 * rule is either a NEW element (the map search, which he asked for on 13 Nov, after
 * approving the design) or the small amount of plumbing a static prototype can do
 * without and a WordPress template cannot.
 *
 * If a rule here ever changes how an approved element looks, it belongs in the mockup
 * instead — where he can see it before it ships.
 * ========================================================================= */

/* --- plumbing -------------------------------------------------------------
 * The prototype hard-coded its logo and navigated by swapping screens. A real
 * header wraps the logo in a link, and a real listing hides cards rather than
 * rebuilding the grid — and `.card{display:flex}` beats the `hidden` attribute,
 * which is a trap worth closing explicitly.
 */
.logo-link { display: inline-flex; text-decoration: none; }
.card[hidden] { display: none; }

/* The sort control is a form here, because it has to carry the current filters with
 * it. `display:contents` keeps the <select> a direct flex child of `.rhead`, so the
 * approved `margin-left:auto` still pushes it to the right. */
.sortform { display: contents; }

/* Nine properties have no photograph at all. An honest empty tile reads better than
 * a broken image, and it keeps the card the same height as its neighbours. */
.card-nophoto {
  position: absolute; inset: 0; display: grid; place-items: center;
  background: var(--surface-2); color: var(--muted);
  font-size: 12.5px; letter-spacing: .08em; text-transform: uppercase;
}

/* --- the ficha map --------------------------------------------------------
 * `.map` draws a stand-in grid with a ::before. With a real map inside it, that
 * grid would sit under the tiles doing nothing, so it is switched off — and the
 * caption, which the design positions over the bottom edge, is lifted above the
 * tiles rather than being covered by them.
 */
.map:has(.map-live)::before { content: none; }
.map-live { position: absolute; inset: 0; z-index: 0; }
.map figcaption { z-index: 1; }

/* --- the map search -------------------------------------------------------
 * NOT part of the approved mockup. He asked for it on 2026-11-13: pan and zoom
 * over the La Plata grid, with the list following the viewport. It is deliberately
 * additive — closed by default, above the grid, moving nothing.
 */
.search-map {
  height: 460px; margin-bottom: 18px;
  border: 1px solid var(--line); border-radius: var(--radius);
  overflow: hidden; background: var(--surface-2);
}
@container (max-width: 700px) { .search-map { height: 340px; } }

.rhead #map-toggle { margin-left: auto; }
.rhead select { margin-left: 0; }

.map-note { color: var(--warn); margin: -8px 0 14px; }
.map-count b { font-variant-numeric: tabular-nums; }

/* The popup: a photograph, a price and a title, behaving like a small card. */
.map-pop { display: block; width: 180px; text-decoration: none; color: inherit; }
.map-pop img {
  width: 100%; height: 110px; object-fit: cover;
  border-radius: 6px; margin-bottom: 6px;
}
.map-pop b { display: block; font-size: 14px; color: var(--navy); }
.map-pop span { display: block; font-size: 12.5px; color: var(--muted); line-height: 1.35; }

/* Leaflet paints its own controls; these two only align it with the design's
 * neutrals so the map does not look pasted in. */
.leaflet-container { font-family: var(--sans); background: var(--surface-2); }
.leaflet-popup-content { margin: 10px; }

/* --- the capped thumbnail strip ------------------------------------------
 * CF4 has 158 photographs. The prototype's ficha was drawn with a handful, so
 * it never had to answer what a strip of 158 does to a phone: 217 KB of HTML
 * before a single picture loads. The strip stops at two dozen and this line
 * says how many more there are, so the number is honest rather than hidden.
 */
.gthumbs-rest { margin: 8px 0 0; color: var(--muted); }
