feat(facts): phase 13 - per-game facts, Rust and RunicNPC checked, main green again

platform.json drops the single protocol/bundle/capability list for a
`games` object (uo, rust) plus a `runicnpc` block. checkFacts.mjs loops
the protocol, plugin-protocol, capability and bundle checks over both
games, reads the schema-2 bundles at v2/<game>/current.json, checks each
module's coreApi, and reads RunicNPC's plugin.toml. 41 facts, up from 19;
clears the two that were red on main (Module API 1.17.0, installer
v0.8.0).

D66: the hero, footer and structured data show the Module API only; each
game's protocol and bundle go on that game's pages, and the docs landing
table splits into shared versions plus one column per game.

The re-read section 1 requires found, and this fixes:
- three hard-coded "1.6.0" Module API versions in the module docs
- module-lifecycle saying modules load alphabetically (the loader now
  refuses a second module, W19), and the install pages never mentioning
  the one-module rule
- "there is one module" in five places, now two modules both built
  inside this project; the Integration Kit keeps its draft banner
- the homepage diagram's ServUO/uo-link sub-labels (D63 wording now)

notBuilt drops `second-module` (resolved by Module-Rust's release) and
rewords `multi-module`.

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

src/components/home/Capabilities.astro

@@ -17,7 +17,7 @@ import { capabilityGroups, assertCapabilityCoverage } from '../../data/capabilit
  * what exists while quietly omitting the well-known things that do not is the exact failure
  * §1 is written to prevent.
  */
-assertCapabilityCoverage(platform.moduleUoCapabilities);
+assertCapabilityCoverage(platform.games.uo.module.capabilities);
 ---
 
 <section class="page section caps">
@@ -52,7 +52,7 @@ assertCapabilityCoverage(platform.moduleUoCapabilities);
 
   <p class="caps__foot prose">
     Some things people reasonably expect are <strong>deliberately not built</strong> — a Matrix
-    integration, more than one game module active at once, a second game module. They are
+    integration, more than one game module active at once, a finished Integration Kit. They are
     listed rather than left out, on <a href="/features/">features</a> and{' '}
     <a href="/integrations/">integrations</a>.
   </p>

src/components/home/DataPath.astro

@@ -1,12 +1,10 @@
 ---
-import platform from '../../data/platform.json';
-
 /**
  * The data path (PLAN.md §13 phase 3), drawn as inline SVG per §11's motif rule — hand-drawn
  * geometry, used where it explains something, and no raster anywhere.
  *
  * ---------------------------------------------------------------------------------------
- * THE LABELS ARE GENERIC, WITH UO AS THE CAPTION
+ * THE LABELS ARE GENERIC; THE CAPTION NAMES THE GAMES
  * ---------------------------------------------------------------------------------------
  * The org lead settled this before the diagram was drawn. The nodes say "your game server"
  * and "sidecar", not "ServUO shard" and "uo-link", because §10's rule is that a reader
@@ -14,10 +12,12 @@ import platform from '../../data/platform.json';
  * repositories in order to connect a game server — and because the tagline promises a
  * platform, not a UO product.
  *
- * It does NOT hide what actually ships. The sub-labels and the caption name ServUO and
- * uo-link outright, because §1 says the technical truth wins and today there is exactly one
- * implementation of this shape. An operator running a shard has to see themselves in the
- * picture on the first screen.
+ * It does NOT hide what actually ships: the caption names the games that ship on this shape,
+ * because §1 says the technical truth wins and an operator has to see their game in the
+ * picture on the first screen. Until phase 13 the sub-labels named ServUO and uo-link, which
+ * was true while there was exactly one implementation. With two, naming one would mislead,
+ * and D63 (PLAN.md §16) keeps each game's vocabulary on that game's own pages — so the
+ * caption names the games and the diagram names nothing else.
  *
  * ---------------------------------------------------------------------------------------
  * WHY THE SVG IS aria-hidden
@@ -74,11 +74,11 @@ import platform from '../../data/platform.json';
 
         <rect class="node" x="20" y="16" width="340" height="76" rx="12" />
         <text class="node-title" x="42" y="50">Your game server</text>
-        <text class="node-sub" x="42" y="72">ServUO today · opens no inbound port</text>
+        <text class="node-sub" x="42" y="72">opens no inbound port</text>
 
         <rect class="node" x="20" y="148" width="340" height="76" rx="12" />
         <text class="node-title" x="42" y="182">Sidecar</text>
-        <text class="node-sub" x="42" y="204">uo-link · the only network-facing part</text>
+        <text class="node-sub" x="42" y="204">the only network-facing part</text>
 
         <rect class="node node--self" x="20" y="280" width="340" height="76" rx="12" />
         <text class="node-title" x="42" y="314">Runic Gateway</text>
@@ -90,8 +90,9 @@ import platform from '../../data/platform.json';
       </svg>
 
       <p class="datapath__caption">
-        Today that game server is a ServUO shard and that sidecar is uo-link. The shape is the
-        contract; the implementations are what plug into it.
+        Two games ship on this shape today, Ultima Online and Rust, each with its own plugin
+        and its own sidecar. The shape is the contract; the implementations are what plug
+        into it.
       </p>
     </div>
 
@@ -109,8 +110,8 @@ import platform from '../../data/platform.json';
         <h3>The sidecar</h3>
         <p>
           A small service beside the game, and the only piece of the bridge anything else can
-          reach. It speaks a versioned wire protocol — protocol {platform.protocol} today — so
-          a mismatched pair is refused rather than misread, and it answers only your website's
+          reach. It speaks a versioned wire protocol — each game pins its own — so a
+          mismatched pair is refused rather than misread, and it answers only your website's
           backend, over an authenticated WebSocket and REST.
         </p>
       </li>

src/components/home/Hero.astro

@@ -55,9 +55,9 @@ import platform from '../../data/platform.json';
       </div>
 
       <div class="chips">
-        <span class="chip chip--version">Protocol {platform.protocol}</span>
+        {/* D66: only the version every deployment shares. A protocol and a bundle belong
+            to a game, so they live on that game's pages rather than on the front door. */}
         <span class="chip chip--version">Module API {platform.moduleApi}</span>
-        <span class="chip chip--version">Bundle {platform.bundle.tag}</span>
       </div>
     </div>