feat(site): phase 17 - per-game module pages, /runicnpc/, and checkTerms over the built site

PLAN.md §16 phase 17, built on the org lead's answers of 2026-10-22,
recorded as D75-D79 (count of record 79).

- D75: core marketing pages describe what a game module adds in core's
  words. "Game intelligence" became "What a game module adds"; each
  game's own list moved to src/data/games/ and renders only on the new
  /modules/uo/ and /modules/rust/. /modules/ is a card per game.
- The page-side capability check is per game (assertGameCoverage), the
  item phase 13 moved here.
- D76: the homepage keeps its game screenshot, labelled. screens.mjs
  entries may carry `game` (D67); Screenshot.astro and the app grid
  print the game's name and mark the figure data-game.
- D77: /app/ describes the Rust screens (released the same day).
- D78: /runicnpc/, the standalone page, is in the header and footer;
  the narrow header was re-measured so five links keep two rows.
- D79: checkTerms.mjs --built reads every built page's visible text
  after the build; game routes and data-game elements allow their
  game's words. Proven against ten plants. Still the twelfth check.
- Re-read fixes: /architecture/'s "two machines is also the maximum",
  Discord "guild" on /integrations/, and collection.mjs against what
  Steam sign-in and the Rust module keep (PLAY_DATA_SAFETY.md
  regenerated; the Play answers are unchanged).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

src/components/Screenshot.astro

@@ -1,5 +1,6 @@
 ---
 import { screenById, WEB, PHONE } from '../data/screens.mjs';
+import platform from '../data/platform.json';
 
 /**
  * One screenshot, as a figure with its caption. PLAN.md §13 phase 9, D4 / D44.
@@ -44,9 +45,16 @@ const src = `/screens/${shot.id}.webp`;
 // taken at one geometry (see screens.mjs), and `checkScreens.mjs` asserts the files really
 // are that size, so these attributes cannot drift from the pixels.
 const { width, height } = shot.family === 'web' ? WEB : PHONE;
+
+// D67: a game's screen says whose it is. The name comes from `platform.json`, as
+// GameExample's does, so the label cannot disagree with the tag the check reads.
+const game = shot.game ? platform.games[shot.game] : null;
+if (shot.game && !game) {
+  throw new Error(`Screenshot "${id}" is tagged game "${shot.game}", which platform.json does not have`);
+}
 ---
 
-<figure class="shot">
+<figure class="shot" data-game={shot.game}>
   <img
     src={src}
     alt={shot.alt}
@@ -55,7 +63,14 @@ const { width, height } = shot.family === 'web' ? WEB : PHONE;
     loading="lazy"
     decoding="async"
   />
-  {!bare && <figcaption>{shot.caption}</figcaption>}
+  {
+    (game || !bare) && (
+      <figcaption>
+        {game && <span class="shot__game">{game.name}</span>}
+        {!bare && shot.caption}
+      </figcaption>
+    )
+  }
 </figure>
 
 <style>
@@ -78,4 +93,18 @@ const { width, height } = shot.family === 'web' ? WEB : PHONE;
     font-size: 0.9rem;
     line-height: 1.5;
   }
+
+  /* The game's name, ahead of the caption (D67). Styled here rather than with the global
+     chip, because the docs pages render this component without the marketing stylesheet. */
+  .shot__game {
+    display: inline-block;
+    margin-right: 0.5rem;
+    padding: 0.05rem 0.55rem;
+    border: 1px solid var(--line);
+    border-radius: var(--radius-pill);
+    color: var(--muted);
+    font-size: 0.76rem;
+    letter-spacing: 0.04em;
+    white-space: nowrap;
+  }
 </style>