Refresh main branch documentation

launcher/README.md

@@ -34,7 +34,7 @@ launcher/
     ├── VersionsManifest.cs    Fetches versions.json from main
     ├── ReleaseDownloader.cs   GitHub Releases API + artifact unpack
     ├── ServerProcess.cs       Spawns the downloaded server binary
-    ├── ClientPatcher.cs       Invokes install-plugin.ps1 from the unpacked patcher
+    ├── ClientPatcher.cs       Applies the manifest-based patcher zip
     ├── LocaltunnelInstaller.cs Downloads the Localtunnel .NET client
     ├── LocaltunnelTunnel.cs    Spawns the tunnel + parses the *.loca.lt URL
     ├── RecRoomPicker.cs       Microsoft.Win32.OpenFolderDialog
@@ -67,7 +67,7 @@ launcher release workflow once it exists).
 
 ## Dependencies on per-version branches
 
-The launcher fetches release artifacts from GitHub Releases tagged on
+The launcher fetches release files from GitHub Releases tagged on
 the per-version branches. See [RELEASES.md](RELEASES.md) for the
 exact naming convention each branch must follow.
 

launcher/RELEASES.md

@@ -1,13 +1,13 @@
 # Release artifact contract
 
-The DorkNet Launcher (on `main`) reads
+The launcher on `main` reads
 [`/versions.json`](../versions.json) to find every supported per-version
-branch, then fetches release artifacts from each branch's GitHub
+branch, then fetches release files from each branch's GitHub
 Releases.
 
-Per-version branches must publish releases that follow this contract,
-otherwise the launcher reports "no release found" / "manifest missing"
-to users on host / join.
+Per-version branches need releases that follow this contract. If the
+assets are missing or named differently, users will see "no release
+found" or "manifest missing" when they host or join.
 
 ## Tag naming