/* =====================================================================
   MESA QUANTUM — DESIGN SYSTEM (NEXT) · CAPABILITY GRAPHICS
   Nine original line pictograms, one per subject. See README.md for the
   drawing-language spec, the depiction sentence for each, and the
   motion-manifest.json fragment you must paste in before enabling motion.

   These are NOT motifs. A motif is decorative and carries aria-hidden.
   These depict a named subject, so they carry a real accessible label
   and they are content (design-guidelines §4 "Iconography").

   INLINE THEM. Do not reference an .svg from `src` or from CSS
   `background-image`. An SVG loaded as a separate document resolves
   `currentColor` against its own root, not the host page — that is the
   defect motifs.css already had to fix for contour.svg, and every file
   here paints with currentColor exclusively.
   ===================================================================== */

.g {
  /* opacity tiers: hierarchy is carried by these, never by stroke weight */
  --g-field: 0.26;      /* the ground being measured: graticule, contours, hatch */
  --g-context: 0.55;    /* the apparatus: satellites, cells, mirrors, rails */
  --g-subject: 1;       /* the thing the adjacent copy claims: the measurement */

  display: block;
  width: 100%;
  height: auto;
  color: inherit;           /* every mark is currentColor */
  overflow: hidden;   /* an SVG must never paint outside its own viewBox onto a neighbour */
}

.g .g-field   { opacity: var(--g-field); }
.g .g-context { opacity: var(--g-context); }
.g .g-subject { opacity: var(--g-subject); }

/* Light ground vs dark ground.
   A dark mark on white reads heavier than a white mark on near-black at
   the same alpha, so the tiers are lifted on dark rather than the colour
   being changed. Apply on the SVG or on any ancestor. */
.g--on-dark, .g--on-dark .g { --g-field: 0.34; --g-context: 0.66; }

/* Optional: tint the measurement itself with the theme accent. Sets
   `color`, so both currentColor strokes and currentColor fills follow. */
.g--accent .g-subject { color: var(--ds-accent, currentColor); }

/* Sizing helper. The family is 3:2; give it a column, not a full bleed. */
.g--inline { max-width: 34rem; }

/* =====================================================================
   MOTION LAYER REMOVED IN THIS VENDORED COPY — a build-local prune, not a fork.

   Upstream design-system-next/graphics/graphics.css ships six @keyframes
   (g-traverse, g-flown, g-anomaly-resolve, g-into-step, g-step-scan,
   g-tested-reveal) that are inert until a `.g--live` class is added to the SVG
   root. Upstream's own README says that class arrives from an
   IntersectionObserver. THIS SITE SHIPS NO JAVASCRIPT AT ALL, so `.g--live` can
   never be applied and none of those six animations can ever run.

   The audit's motion detector reads every .css file in the tree, not only the
   linked ones, so shipping them would oblige motion-manifest.json to declare six
   animations that do not animate. Six paragraphs describing motion nobody can
   see is worse than no paragraphs: it is a manifest that lies. So the block is
   deleted here rather than declared, and this note is the record of the delete.

   Nothing else in this file is changed. To re-enable the graphics motion layer,
   restore the block from design-system-next and add a real `.g--live` trigger
   plus the manifest entries in the upstream README §5 fragment.

   The reduced-motion guard the block carried went with it; with no animation
   left in this file there is nothing for it to switch off. The site's one
   remaining animation, and the hero, are guarded in motifs.css and site.css.
   ===================================================================== */