Add portable Windows desktop downloads and release uploads

docs/vercel-deployment.md

@@ -1,5 +1,17 @@
 # Deploy MineGeo
 
+The portable Windows Electron client and release process are described in
+[Desktop client](desktop.md). Build and publish the EXE before deploying changes
+to desktop download links. Public desktop releases are included in the upload;
+the local Electron source, build cache, and packaging toolchain are excluded.
+
+For the Vercel plugin deployment of Desktop 1.0.0, the public installer parts
+are staged in Supabase Storage's `minegeo-desktop-builds` bucket under the
+release SHA-256. The deployment snapshot downloads and verifies each part before
+the existing assembly script verifies the complete EXE. Keep these immutable
+parts for rebuilding that snapshot. No Storage credentials are included in the
+snapshot, and players download the assembled EXE from `/desktop/` on MineGeo.
+
 Optional Discord map and multiplayer-party announcements use `DISCORD_BOT_TOKEN`,
 `DISCORD_MAPS_CHANNEL_ID`, and `DISCORD_PARTIES_CHANNEL_ID`. All published parties
 use the same configured channel. Follow [Discord bot setup](discord-integration.md)
@@ -19,7 +31,8 @@ invite links. Blank, malformed, or unsupported URLs hide the corresponding
 button. Each button opens its configured destination in a new tab.
 
 Run `npm run deploy` from the project directory. The script collects all web
-source files and public assets, uploads them in one request, waits for the build,
+source files and public assets, uploads large release files separately and the
+remaining source in one request, waits for the build,
 and prints the deployment URL. It uses the [Vercel deployments API](https://vercel.com/docs/rest-api/deployments/create-a-new-deployment). The database credentials already configured in
 Vercel remain there. Mod captures are processed by the deployed Vercel API:
 upload finalization starts background image processing with Next.js `after`,