package dedicated server beta artifacts for Windows and Linux

[MhaWay]

This PR updates the beta dedicated server packaging by creating separate folders for Linux and Windows inside Server-beta.zip.

The main goal is to allow Windows users to run the standalone server directly via Server.exe, instead of receiving only the Linux-style host binary with no .exe extension.

Changes included:

• creation of separate folders for Linux and Windows in the server beta archive
• publish a win-x64 server build so Windows users get Server.exe
• publish a linux-x64 server build and add Server.sh for quick startup on Linux
• update the beta release notes to explain the new layout

Validation:

• validated local dotnet publish for both win-x64 and linux-x64
• confirmed the Windows output contains Server.exe
• confirmed the Linux output contains the expected runtime files plus Server.sh

[Copilot]

Pull request overview

This PR updates the CI workflow that produces the Continuous (“beta”) artifacts so the standalone dedicated server is packaged with separate per-platform outputs, enabling Windows users to run Server.exe directly while also providing a Linux startup script.

Changes:

• Publish dedicated server builds for win-x64 and linux-x64 into output/Server/Windows and output/Server/Linux.
• Add a Linux Server.sh launcher and package both platforms into a new Server-beta.zip.
• Update release notes with standalone server setup instructions reflecting the new zip layout.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/build-beta.yml	Adds server publish steps for Windows/Linux, creates Server-beta.zip, and uploads it to the Continuous release.
.github/workflows/alpha-notes.md	Documents the new Server-beta.zip layout and startup instructions for Windows and Linux.

Comments suppressed due to low confidence (1)

.github/workflows/build-beta.yml:68

• The uploaded artifact is named Multiplayer-beta but path: output/ now contains both the mod files and the newly published Server/ outputs. This makes the artifact name/content mismatched and harder to find/consume. Consider renaming the artifact to reflect both (or restrict path to output/Multiplayer if the server output shouldn't be part of the artifact).

    - name: Upload Mod Artifacts
      uses: actions/upload-artifact@v4
      with:
        name: Multiplayer-beta
        path: output/

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.