/* ════════════════════════════════════════════════════════════════════════
   screenshots.css — the app-screenshot gallery on About.aspx.

   Added 2026-08-07, mirroring the sheet qFIT introduced on 2026-08-06 so the
   three sites present their product the same way. Loaded per page through
   AssetUrl(), which stamps the file's mtime as ?v=, so editing it is
   self-busting and the service-worker CACHE_VERSION does NOT need a bump.

   ── WHY 390px ─────────────────────────────────────────────────────────────
   Each file in ~/Images/screens is 780 x 920: a real 390 x 460 CSS phone
   viewport captured at deviceScaleFactor 2. The widest it may ever be
   DISPLAYED is therefore 780 / 2 = 390 CSS px, and `.shot` caps at exactly
   that — at or under 390px the image is always at least 2x on a retina
   screen and is never upscaled past its own pixels. Re-export at a different
   width and this number moves with it; they are a pair.
   ⚠ qFIT's copy of this sheet says 389px, not 390. That is not drift: its
   shots are 778 wide because they were captured a different way. Read the
   file's real pixel width before changing either number.

   ── WHY THE 3-UP GRID STARTS AT 1024px, NOT 768px ─────────────────────────
   Shared `.about-grid-3` goes three-across at 768px, which is too early for
   this content: a three-column column inside a .main-card is ~257px there,
   which renders a 390px-wide phone UI at 0.66 scale and drops its 16px body
   text to ~10.5px — legible as a shape, not as words. 1024px is the first
   viewport where a column clears ~300px. Under it the figures stack, centerd,
   at full size.

   ── WHAT IS DELIBERATELY NOT HERE ─────────────────────────────────────────
   No image CDN and no lazy-loading library. The markup's `loading="lazy"` and
   `decoding="async"` are plain HTML attributes and the files are served from
   ~/Images/screens like every other asset. Responsive sizing needs no rule
   here either — styles_shared.css already sets
   `img, svg { max-width: 100%; height: auto; }` site-wide; `.shot img` only
   adds the frame.
   ════════════════════════════════════════════════════════════════════════ */

.shot-grid {
    display: grid;
    grid-template-columns: 1fr;
    gap: 1.5rem;
    justify-items: center;
}

@media (min-width: 1024px) {
    .shot-grid {
        grid-template-columns: repeat(3, minmax(0, 1fr));
        align-items: start;
    }
}

/* <figure> ships with a browser default margin; drop it so the grid gap is the
   only spacing in play. */
.shot {
    margin: 0;
    width: 100%;
    max-width: 390px;   /* half of the 780px intrinsic width — see WHY 390px */
}

/* width:100% plus the width/height attributes in the markup means the box is
   reserved from the 780:920 ratio before the bytes arrive, so `loading="lazy"`
   cannot shift the page as each shot loads. */
.shot img {
    display: block;
    width: 100%;
    border-radius: 12px;
    border: 1px solid var(--color-border);
    box-shadow: 0 2px 10px rgba(0, 0, 0, 0.12);
}

.shot figcaption {
    margin-top: 0.6rem;
    font-size: 0.9rem;
    line-height: 1.35;
    color: var(--color-text-muted);
    text-align: center;
}