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

README.md

@@ -56,7 +56,7 @@ that would otherwise decay quietly.
 
 ```bash
 npm run check:sidebar                             # the rendered docs tree still matches the planned one
-npm run check:terms                               # no game's vocabulary outside that game's section
+npm run check:terms                               # no game's vocabulary outside its section: docs + sidebar
 npm run check:screens                             # every screenshot has an entry, at the size declared
 npm run check:tokens                              # no colour literal outside the token file
 npm run check:brand                               # the branding pipeline's two quiet failures
@@ -65,6 +65,7 @@ npm run check                                     # astro check
 npm test                                          # the beta signup's decision path, and the policy data
 npm run build                                     # everything below reads the build
 npm run check:links                               # every internal link resolves
+npm run check:terms:built                         # the same rule over every built page, as rendered
 GITEA_TOKEN=<token> npm run check:facts           # every version agrees with its authority
 GITEA_TOKEN=<token> npm run check:quickstart      # the install page still matches website's own files
 GITEA_TOKEN=<token> npm run check:reference       # every name the Reference lists still exists
@@ -229,11 +230,15 @@ src/
   data/collection.mjs    What is collected, in three scopes. /privacy renders it and the
                          Play Data Safety notes are generated from it — one inventory.
   data/legal.mjs         The values /terms, /privacy and the consent sentence must share.
+  data/games/            One file per game, in that game's words, checked against its
+                         module's capabilities. Only that game's pages render it.
   styles/tokens.css      THE token file — the only place a colour literal may appear.
   styles/global.css      The layout shell, built entirely from tokens.
   styles/starlight.css   Restates our tokens as Starlight's, so the docs cannot drift.
   layouts/, components/  The marketing chrome.
   pages/                 Marketing routes.
+  pages/modules/         One page per game module; with /runicnpc/, the only marketing
+                         routes that may use a game's own words (D63, checkTerms --built).
   pages/beta.astro       The signup. Renders AND handles its own POST — runs per request.
   content/docs/docs/     Documentation. The extra level mounts Starlight at /docs.
   pages/brand/           GET /brand/* — the mount, resolved and derived. Runs per request.