Build local release artifacts and prepare Compose deployment [skip ci]

release-artifacts/0.4.0/README.md

@@ -0,0 +1,20 @@
+# Local 0.4.0 build artifacts
+
+These files were built from PR #3 source with GitHub Actions disabled.
+
+- `SCOPENET Launcher_0.4.0_x64-setup.exe`: Windows x64 NSIS installer,
+  cross-compiled on macOS with Tauri and cargo-xwin. It is unsigned and asks
+  the player for the panel URL on first launch.
+- `scopenet-fabric-{1.20.1,1.21.1,26.3}-0.4.0.jar`: server-side Fabric mods.
+- `scopenet-forge-{1.20.1,1.21.1,26.3}-0.4.0.jar`: server-side Forge mods.
+- `scopenet-paper-0.4.0.jar`: Paper plugin, built against Spigot API 1.20.1.
+
+The repository has a Forge server mod but no separate NeoForge server mod, so
+these artifacts do not include a NeoForge JAR.
+
+The build commands and integration tests passed locally. Every JAR passed ZIP
+integrity checks and contains its loader descriptor. `SHA256SUMS` records the
+artifact hashes; run `shasum -a 256 -c SHA256SUMS` from this folder to verify.
+
+Minecraft client/server runtime testing and installation of the Windows
+installer on Windows still need to be done before a public release.

release-artifacts/0.4.0/SHA256SUMS

@@ -0,0 +1,8 @@
+e8578861c71edaf4ffe8d6e4edad98c048a0d595e67196041a484eaa2e1bd6fe  SCOPENET Launcher_0.4.0_x64-setup.exe
+3dd93d31de1bf82d4e5e81a6f964b6f7179b44f4cc47e8ebed7e9751c8022d48  scopenet-fabric-1.20.1-0.4.0.jar
+fb7ac37ed2313ec489f0b355b074904809fdec6a271b4c1e0d545f6f88cde9e2  scopenet-fabric-1.21.1-0.4.0.jar
+2ef7eef23bfbe6731372cba76a433e3201d3a080d24d0567094b1c59f998740b  scopenet-fabric-26.3-0.4.0.jar
+1c8256bb3cef5ebc44090b891e1588c04c78158170b81b2a853a11f8b64b4561  scopenet-forge-1.20.1-0.4.0.jar
+e94fbd0bc76a8a93a284d6bbf8a52db8fa014dd702c4159278bee0dfe71afdaa  scopenet-forge-1.21.1-0.4.0.jar
+9a1f4c5796f582a7c636226b72467fc5b734519a0ac845c6c2b33ba0898b738c  scopenet-forge-26.3-0.4.0.jar
+75560c64d08b512dc53845a0da7de468d01951963af02d10fd0b236f1e71e4f8  scopenet-paper-0.4.0.jar