/* ════════════════════════════════════════════════════════════════════════
   screenshots.css — the app-screenshot gallery on the ANONYMOUS pitch
   (Home.aspx's pnlAnonymous branch and About.aspx).

   Added 2026-08-06. Before this, Home / About / Join1 / Login / QuickStart
   contained zero <img> tags and qFIT\Images held no product shot at all, so a
   visitor decided whether to join without ever seeing the app.

   ── WHY 389px ─────────────────────────────────────────────────────────────
   Each file in ~/Images/screens is 778 x 920 and was exported at 2x, so the
   widest it may ever be DISPLAYED is 778 / 2 = 389 CSS px. `.shot` caps at
   exactly that: at or under 389px the image is always at least 2x on a retina
   screen, and it is never upscaled past its own pixels. If you re-export the
   shots at a different width, change this number with them — they are a pair.

   ── WHY THE 3-UP GRID STARTS AT 1024px, NOT 768px ─────────────────────────
   The obvious move is to reuse shared `.about-grid-3`, which goes three-across
   at 768px. Measured, that is too early: at a 768px viewport a three-column
   column inside a .main-card is ~257px, which renders this 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
   (~0.77 scale, ~12px text). Under it the figures stack, centred, 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 does not need a
   rule here either — styles_shared.css:534 already sets
   `img, svg { max-width: 100%; height: auto; }` site-wide; `.shot img` only
   adds the frame. Both hosts load this sheet 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 (that list covers only
   assets loaded WITHOUT AssetUrl).
   ════════════════════════════════════════════════════════════════════════ */

.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: 389px;   /* half of the 778px intrinsic width — see WHY 389px */
}

/* width:100% + the width/height attributes in the markup means the box is
   reserved from the 778: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;
}
