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/architecture/ModuleSeam.astro

@@ -26,8 +26,8 @@ import platform from '../../data/platform.json';
     <p class="eyebrow">Where the game stops</p>
     <h2>A seam, with a version on it</h2>
     <p class="prose">
-      The core site does not know what a shard is, what a guild is, or that Ultima Online
-      exists. Everything that does lives in an installable module on the other side of a
+      The core site does not know what game it serves, what that game calls a group of
+      players, or that Ultima Online and Rust exist. Everything that does lives in an installable module on the other side of a
       declared interface — which is what makes "put your game on it" a shape rather than a
       slogan.
     </p>
@@ -123,8 +123,8 @@ import platform from '../../data/platform.json';
         <p>
           Core owns the Teams primitive — the roster, the forum, the notifications, the voice
           channel — and does not own the <em>word</em>. A Team cannot be created in core at
-          all; it arrives from the module, which is why the UO module calls them guilds and
-          builds those pages itself. That is the pattern the whole interface is built on: core
+          all; it arrives from the module, which is why each module calls them by its own
+          game’s word and builds those pages itself. That is the pattern the whole interface is built on: core
           supplies the machinery, the module supplies the meaning.
         </p>
       </section>