fix(facts): installer v0.1.1 is released, so the note names a version

Recovering installer's orphan tag published v0.1.1, which moved the platform
under this branch and turned checkFacts red -- the check working exactly as it
should, since a version this site quotes had changed.

  FAIL  release installer
        platform.json says : v0.1.0
        installer releases/latest says : v0.1.1

The 500 that orphaned the tag was a race with the tag push one second earlier,
not a structural failure: re-running the workflow took the built-in orphan-tag
recovery path and published all four assets unchanged.

So the stale-path Aside stops saying "v0.1.0 is still the current download",
which is no longer true, and says the durable thing instead -- v0.1.0 prints
the old path, v0.1.1 prints the real one -- which stays correct however many
releases follow. platform.json and the PLAN.md version table move to v0.1.1,
and the phase 7 findings record the pipeline defect as a fourth finding.

Co-Authored-By: Claude <noreply@anthropic.com>

src/content/docs/docs/getting-started/connect-a-game-server.mdx

@@ -107,14 +107,16 @@ sidebar — `/admin/uo/link`. Tick *Enable the shard integration*, paste **Base
 immediately.
 
 <Aside type="caution" title="Installer v0.1.0 prints an older path for that screen">
-It prints `…/admin/shard`. Since the shard screens became part of the `uo` module — and a
-module owns one path segment wherever it appears — the screen moved to **`/admin/uo/link`**.
+v0.1.0 prints `…/admin/shard`. Since the shard screens became part of the `uo` module — and
+a module owns one path segment wherever it appears — the screen moved to
+**`/admin/uo/link`**.
 
 The old path does not fail visibly: the site has no route for it, so it sends you to the
 dashboard, and that looks like the link worked. The four values you were just told to paste
 then have nowhere to go. Use the sidebar, or the path above.
 
-Corrected in the installer's `main`; v0.1.0 is still the current download.
+Fixed in **v0.1.1**, which prints the real path. Only matters if you are running the older
+binary.
 </Aside>
 
 The token is encrypted at rest and **never returned to any client** — losing it means

src/data/platform.json

@@ -27,7 +27,7 @@
 
   "releases": {
     "link": "v2.0.0",
-    "installer": "v0.1.0",
+    "installer": "v0.1.1",
     "Module-uo": "v1.0.1",
     "Android-app": "v0.5.0"
   },