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

@@ -8,9 +8,11 @@ import platform from '../../data/platform.json';
  * The other two draw runtime shapes. This one draws a code boundary, and it is here because
  * it is the claim the whole project rests on: that a community platform can be built once
  * and pointed at any game. An evaluator has every reason to read that as marketing, so the
- * page draws the seam and then says plainly what does and does not prove it — one module
- * exists, the second is a paper exercise, and the exit criterion for calling the contract
- * proven is written down (§2, and the entries `/modules/` renders from `notBuilt.mjs`).
+ * page draws the seam and then says plainly what does and does not prove it — two modules
+ * exist, both built inside this project, and the exit criterion for calling the contract
+ * proven by an outsider is written down (§2, §16, and the entries `/modules/` renders from
+ * `notBuilt.mjs`). Until phase 13 this said one module and a paper exercise; Module-Rust's
+ * release made that false.
  *
  * The Module API version is read from `platform.json` like every other number on this site
  * (§12). It is the one place a version genuinely belongs in this diagram: the seam is
@@ -73,7 +75,7 @@ import platform from '../../data/platform.json';
         <!-- The module: everything that knows a game exists. -->
         <rect class="host" x="8" y="306" width="364" height="186" rx="14" />
         <text class="host-title" x="28" y="340">Game module</text>
-        <text class="host-sub" x="28" y="360">one per deployment; UO today</text>
+        <text class="host-sub" x="28" y="360">one per deployment; UO or Rust today</text>
 
         <rect class="node" x="28" y="378" width="156" height="46" rx="10" />
         <text class="node-title" x="46" y="406">Routes</text>
@@ -130,11 +132,12 @@ import platform from '../../data/platform.json';
       <section>
         <h3>What this does not yet prove</h3>
         <p>
-          One module exists and it is Ultima Online. A second, for a different game, is a
-          written dry-run that was deliberately never implemented — it exists to test whether
-          the contract generalises on paper. Until somebody builds the second one, the seam is
-          a well-argued design rather than a demonstrated one, and this site says so wherever
-          it comes up.
+          Two modules exist: Ultima Online, and Rust, which this project built second, from
+          the Integration Kit. Where the Rust module needed something the contract did not
+          yet offer, the gap was closed in core, for every module, rather than in a fork — so
+          the seam now has two games on its far side instead of one. What two modules built
+          inside this project cannot prove is that somebody outside it can do the same, and
+          that is why the Integration Kit still says draft.
         </p>
       </section>
     </div>