/* ==========================================================================
   TYPE WEIGHT OVERRIDE
   --------------------------------------------------------------------------
   Owner review: landing body copy "is really light, like it's not bold, like
   the previous version was a bit bolder" -- reported against the /oss/ card
   text ("Fully automated scanner for detecting Log4Shell..."), and asked for
   as a site-wide pattern at the SAME SIZE.

   The incumbent agrees: master set body prose at 450, not 400
   (`.pa-table tbody td`, `.pc-card__*` in pricing/asm.html and
   pricing/console.html). The migration flattened it to 400 via
   `--l-fw-regular`, and 400 Urbanist on a dark ground is where the thinning
   shows -- light-on-dark always reads lighter than the same weight
   dark-on-light.

   THIS IS AN OVERRIDE FILE BY INSTRUCTION. `--l-fw-regular` and the existing
   `font-weight` declarations are deliberately left untouched: the owner asked
   for the weight to be corrected by a layer on top rather than by editing the
   type scale in place, so the base contract still reads 400 and this sheet is
   the single place the correction lives. Delete this file and the link in
   base_v2.html to revert completely.

   Loaded LAST of the seven sheets but declared into the `base` layer, so it
   outranks `fh-base.css`'s `body` rule (same layer, later declaration) while
   still yielding to `components`, `patterns`, `utilities` and `page` -- every
   component that names its own weight keeps it, and no page override is
   disturbed.
   ========================================================================== */
@layer base {
  /* 450, the incumbent's own body weight. Size, line-height, tracking and
     colour are all untouched -- this changes one axis only. Urbanist is loaded
     as a variable font (`wght@0,300..800`, base_v2.html:34), so 450 is a real
     instance and not a synthesised one. */
  body {
    font-weight: 450;
  }
}

@layer components {
  /* MONO STAYS AT ITS CUT.

     JetBrains Mono is NOT variable here -- base_v2.html:34 requests three
     discrete cuts, `wght@400;500;700`. CSS font matching resolves a request
     of 450 against a family with no 450 by searching UPWARD first for a
     desired weight in 400-500, so every mono readout that merely inherits its
     weight would have jumped to the 500 cut: soundings, coordinates, JSON,
     endpoint paths, the query input. That is a register change, not a
     legibility fix -- The Mono Is Measurement Rule wants machine output to
     look like machine output, and 500 reads as emphasis.

     Declared in `components` so it lands with the classes it corrects and
     still loses to any component that asks for 500 or 700 on purpose (the
     endpoint verb, the code key). */
  .fh-code,
  .fh-endpoint,
  .fh-entry__input,
  .fh-table__num {
    font-weight: 400;
  }
}