/* ──────────────────────────────────────────────────────────────────────────
   Visual Suspect — portfolio v2, HOST INTEGRATION layer.

   vs-portfolio-v2.css is the LOCKED design and is copied verbatim from
   skills/portfolio-creator-v2/design/. It was authored for a standalone page.
   On visualsuspect.co the v2 block is spliced into the Brooklyn theme, whose
   own rules out-specify parts of the contract (Montserrat on every heading, a
   quoted blockquote, a 1320px content well, overflow:hidden on the body).

   This sheet only RESTORES the contract. It adds no design of its own, and it
   is scoped to [data-vs-portfolio-v2] so no other page is touched. Load it
   AFTER vs-portfolio-v2.css. Shared by every v2 page: per-project overrides
   belong in that page's own <style>, not here.
   ────────────────────────────────────────────────────────────────────────── */

/* ── 0. Inter 700 ─────────────────────────────────────────────────────────
   LOCKED-DESIGN rule 2 asks for Inter 400/500/600/700. The site's shared
   vs-fonts.css declares 400, 500 and 600 only, so every display line —
   h1, the facts headline, the pull quote — was being drawn from the 600 face
   and read a weight too light.

   The two faces below add 700 for this page alone. They point at the files
   vs-fonts.css already ships: Google serves ONE variable file for Inter's
   whole range, so 400/500/600 are the same bytes and 700 costs nothing extra
   on the wire. Declaring it here rather than in vs-fonts.css keeps 606 other
   pages, their render-blocking CSS budget and the front page untouched —
   adding it site-wide grew the shared sheet past perf_gate's ceiling. If v2
   ever becomes the whole site, move these two blocks into fetch_fonts.py's
   Inter URL instead. */
@font-face{
  font-family:'Inter';font-style:normal;font-weight:700;font-display:swap;
  src:url(/vs-fonts/Inter-400-latin-ext.woff2) format('woff2');
  unicode-range:U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
@font-face{
  font-family:'Inter';font-style:normal;font-weight:700;font-display:swap;
  src:url(/vs-fonts/Inter-400-latin.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;
}

/* ── 1. Full bleed ────────────────────────────────────────────────────────
   The theme wraps page content in #primary (1320px well, 60px gutters). The
   locked design has two black bands that must run edge to edge. Each section
   inside keeps its own max-width, so only the bands change. width:auto with
   two negative margins fills the viewport exactly, without 100vw's
   scrollbar overshoot. Section 01's root carries an inline width:100%, which
   in the theme's well resolves to 1300px, so the override is !important. */
[data-vs-portfolio-v2]{
  width:auto !important;
  max-width:none !important;
  margin-left:calc(50% - 50vw);
  margin-right:calc(50% - 50vw);
}

/* ── 2. Let the page scroll ───────────────────────────────────────────────
   The theme sets overflow:hidden on #ut-sitebody, which is the BODY. Body
   overflow propagates to the viewport, so hidden — and clip, which was the
   first thing tried here — stops the page scrolling AT ALL. visible is the
   only value that leaves the viewport alone, and section 01's own
   overflow-x:clip already holds the sideways axis the theme's hidden was
   there for. :has() keeps this to pages that actually carry a v2 block.

   (This also used to matter for `animation-timeline: view()`, which a
   non-visible ancestor freezes outright. That engine is retired —
   LOCKED-DESIGN §1.8 — but the scrolling reason stands on its own.) */
#ut-sitebody:has([data-vs-portfolio-v2]){overflow:visible}

/* ── 3. Inter only (rule 2) ───────────────────────────────────────────────
   The theme's heading font is set from an id selector, so this is the one
   place the layer needs !important. The production card's values keep the
   system monospace stack the contract allows them. */
[data-vs-portfolio-v2],
[data-vs-portfolio-v2] *:not(.vsp-value):not(.vsp-status):not(.vsp-meta){
  font-family:'Inter',-apple-system,sans-serif !important;
}
[data-vs-portfolio-v2] .vsp-value,
[data-vs-portfolio-v2] .vsp-status,
[data-vs-portfolio-v2] .vsp-meta{
  font-family:ui-monospace,'SF Mono',Menlo,monospace !important;
}

/* ── 4. The type scale ────────────────────────────────────────────────────
   Two-class selectors (0,2,0) beat the theme's element rules without
   !important, so the sections' own inline margins still win. */
[data-vs-portfolio-v2] .big{
  font-weight:700;
  letter-spacing:-.042em;
  line-height:1.08;
  text-transform:none;
}
[data-vs-portfolio-v2] .body{font-size:18px;line-height:1.65;color:#3a3a3f}
[data-vs-portfolio-v2] .eyebrow,
[data-vs-portfolio-v2] .lbl,
[data-vs-portfolio-v2] .lbld{line-height:1.3}

/* The element resets below are held to elements with NO class of their own,
   so that every rule in the locked stylesheet — .vsp-kicker's margin,
   .vsp-title's weight and colour, .showreel-sound-btn's glass — still wins.
   A blanket `[data-vs-portfolio-v2] p` is (0,1,1) and would quietly out-rank
   all of them. */
[data-vs-portfolio-v2] h1:not([class]),
[data-vs-portfolio-v2] h2:not([class]),
[data-vs-portfolio-v2] h3:not([class]),
[data-vs-portfolio-v2] h4:not([class]),
[data-vs-portfolio-v2] p:not([class]),
[data-vs-portfolio-v2] dl:not([class]),
[data-vs-portfolio-v2] dt:not([class]),
[data-vs-portfolio-v2] dd:not([class]){margin:0;padding:0;text-transform:none}
[data-vs-portfolio-v2] h1,
[data-vs-portfolio-v2] h2,
[data-vs-portfolio-v2] h3,
[data-vs-portfolio-v2] h4{text-transform:none}
[data-vs-portfolio-v2] h3:not([class]){color:#1d1d1f;font-weight:700}

/* Re-assert the two card rules the theme's heading selectors out-rank. */
[data-vs-portfolio-v2] .vsp-title{font-weight:600;color:#f4f5f7;letter-spacing:-.03em;line-height:1}
[data-vs-portfolio-v2] .srow dt{font-weight:600}

/* The theme gives a blockquote a rule, an indent and a pair of quote marks.
   Section 08 is one line of display type and nothing else. */
   The theme's own blockquote rule out-specifies even a two-class selector and
   lands font-weight:400 and a FIXED line-height:34px on it — at 57px type
   that is a 34px line box, which is why the two lines sat on top of each
   other. Weight and leading have to be taken back with !important here.
   Display type that wraps needs a little more leading than the locked 1.08
   single-line figure: 1.14 clears Inter's ascender/descender at 72px. */
[data-vs-portfolio-v2] blockquote{
  margin:0 auto;padding:0;border:0;background:none;font-style:normal;quotes:none;
}
[data-vs-portfolio-v2] blockquote.big{
  font-weight:700 !important;
  line-height:1.14 !important;
  border:0 !important;      /* the theme's 4px rule down the left edge */
  padding:0 !important;     /* and the 40px indent that came with it */
}
/* Same guard for any display line long enough to wrap. */
[data-vs-portfolio-v2] h1.big,
[data-vs-portfolio-v2] h2.big{line-height:1.1}
[data-vs-portfolio-v2] blockquote::before,
[data-vs-portfolio-v2] blockquote::after{content:none;display:none}

/* ── 5. Elements the theme decorates ──────────────────────────────────── */
[data-vs-portfolio-v2] a{text-decoration:none;color:inherit;box-shadow:none}
[data-vs-portfolio-v2] a:hover{text-decoration:none}
[data-vs-portfolio-v2] figure{margin:0;padding:0}
[data-vs-portfolio-v2] img{max-width:100%;border:0;box-shadow:none}
/* .sup / .supd own their own size and lift (rule 5) — only the theme's plain
   <sup> treatment is reset, never theirs. */
[data-vs-portfolio-v2] sup:not(.sup):not(.supd){top:auto;vertical-align:baseline;font-size:11px;line-height:1}
[data-vs-portfolio-v2] button:not([class]){font:inherit;color:inherit;background:none;border:0;border-radius:0;box-shadow:none;letter-spacing:inherit}
[data-vs-portfolio-v2] button{text-transform:none;text-shadow:none;min-width:0}
[data-vs-portfolio-v2] svg{display:inline-block;vertical-align:middle}
[data-vs-portfolio-v2] video{max-width:100%}

/* The theme animates and hover-lifts anything it recognises as a card or a
   section; the v2 block brings its own motion and must not get a second set. */
[data-vs-portfolio-v2] *{animation-delay:0s}
[data-vs-portfolio-v2] .ut_animate_element,
[data-vs-portfolio-v2] .ut-animate{opacity:1;transform:none}

/* ── 6. The facts rail's seven cells ──────────────────────────────────────
   Each cell is a <button>, and a button centres its own content vertically —
   UA behaviour, not anything the locked sheet asks for. The cells are grid
   items and therefore all the same height, so as soon as one value wraps to
   two lines (with seven facts and values like "HKIA and ADB Safegate", three
   of them do) the one-line cells get their whole contents pushed down by half
   a line. Labels and progress rails then stagger across the row by ~13px.

   Lay each cell out from the top instead, and send the rail to the bottom, so
   the seven labels sit on one line and the seven rails on another whatever
   the values do. Not a theme conflict — a locked-design assumption that every
   value fits on one line — but it belongs with the other shared repairs
   rather than in one page's <style>, because it is true of every v2 page. */
[data-vs-portfolio-v2] .fact{
  display:flex;
  flex-direction:column;
  align-items:stretch;
  justify-content:flex-start;
}
[data-vs-portfolio-v2] .fact .track{margin-top:auto}

/* ── 7. A Visuallizer collage used as hero media ──────────────────────────
   The three rules the Collage app's exported markup needs. Copied from the
   export's own <style> block and scoped to the v2 block so they reach no
   other page; the class names stay as the canonical renderer writes them,
   because the markup is spliced verbatim and must never be re-authored.

   GAP LINES ARE WHITE, EVERYWHERE. The export's grid has a gap and no
   background, so its lines show whatever is behind them — and the hero
   straddles the seam, which drew them dark over the black band and white
   below it: one grid, two line colours, reading as holes. The grid is backed
   white so the lines are one colour top to bottom (LOCKED-DESIGN.md §10).
   The cells are backed in the band's black for the opposite reason: until a
   poster arrives a cell is transparent, and a white backing alone would
   paint the whole hero as a white slab on the black band. */
[data-vs-portfolio-v2] .vz-collage{display:grid;position:relative;width:100%;overflow:hidden;background:#ffffff}
[data-vs-portfolio-v2] .vz-collage .vz-cell{position:relative;overflow:hidden;background:#0b0b0c}
[data-vs-portfolio-v2] .vz-collage .vz-media{
  position:absolute;inset:0;width:100%;height:100%;
  object-fit:cover;transform-origin:center;display:block;
}

/* ── 8. The film wall's active chip ───────────────────────────────────────
   The active chip's underline is the page's third #d20000 (rule 4: the nav
   underline, the quote's full stop, and this). The locked sheet draws it as a
   2px bottom border on .vsw-c — and the theme strips every border off every
   <button> with `border:none !important`, so it never rendered: HKIA's live
   wall and Swire's both showed the accent twice. Found 2026-11-18 with
   CSS.getMatchedStylesForNode; getComputedStyle read `0px none`.

   Only !important can answer !important. Higher specificity decides between
   the two, so this wins without touching any other button on the page. */
[data-vs-portfolio-v2] #films .vsw-c{border-bottom:2px solid transparent !important}
[data-vs-portfolio-v2] #films .vsw-c[aria-pressed="true"]{border-bottom-color:#d20000 !important}
