Luminae Cloud Node — legacy Windows candidate 0.1.0

This native .NET application targets Windows 7 SP1 or newer with Microsoft .NET
Framework 4.8 installed. It is separate from the modern Electron Server Manager,
whose Electron runtime does not support Windows 7. This candidate has not been
qualified on the physical Dell. No operating-system upgrade, .NET installation,
TLS bypass, firewall opening, or existing game/world migration runs automatically.

1. Extract the entire download into a folder. Install Microsoft's .NET Framework
   4.8 through Microsoft's official installer if the prerequisite is missing.
   Microsoft lists Windows 7 SP1 as an installation target for .NET 4.8, while
   Windows 7 itself is out of support. Installation compatibility does not
   qualify this application, a game runtime or the physical Dell:
   https://learn.microsoft.com/dotnet/framework/get-started/system-requirements
   https://support.microsoft.com/en-us/servicing/dotnetframework/2019/10/microsoft-net-framework-4-8-offline-installer-for-windows
2. Open Luminae Node.exe. Confirm the real Cloud API address. The configured
   Tailscale address requires both computers to be on the authorized tailnet and
   the existing Cloud API forwarder to be serving. A reachable address alone is
   not an authenticated node identity.
3. Enter the existing Cloud owner/operator account in this private application.
   The app verifies current membership, mints a ten-minute single-use enrollment
   capability, and registers this computer in that account's existing tenant.
   Passwords, login bearer tokens, and enrollment tokens are never saved.
4. The node credential is encrypted with Windows DPAPI for the current Windows
   user under %LOCALAPPDATA%\Luminae\LegacyNode\identity.dpapi. Existing identity
   files are preserved. Changing Cloud or tenant requires an explicit separately
   reviewed migration; the app refuses to overwrite another enrollment.
   If an enrollment response is lost, a protected pending marker prevents a
   second node from being silently registered. ENROLLMENT_OUTCOME_UNKNOWN means
   the owner must reconcile the Cloud node and credential before another attempt;
   the app does not delete that evidence or automatically retry enrollment.
5. Optionally check “Connect automatically when I sign in to Windows.” This
   installs a versioned copy and a visible HKCU Run entry named Luminae Cloud
   Node. It connects at that user's sign-in, not before sign-in and not as SYSTEM.
   Closing a connected main window leaves its visible tray icon running. Use the
   tray's “Disconnect node and exit” to stop connection. Unchecking automatic
   connection on a successful sign-in removes that app's Run entry.
6. Use the Minecraft/FiveM panel for real Cloud create/install/start/stop/health
   commands on this exact enrolled node. Check runtime, free resources, license,
   server-key, EULA and archive requirements in the panel and package evidence.
   Older Windows does not imply current game versions or Java versions work.

The node uses the existing Cloud signed heartbeat/command/result protocol.
Inventory intentionally excludes disk/board serials, MAC addresses, MachineGuid
and GPU identifiers. Game commands are allowlisted by the managed-game adapter.
Unsupported workload/model/OS/shell command types fail and report that result;
they do not execute arbitrary code or become a substitute Lumi/Regulus worker.
Generic workload contributions are advertised as paused with an empty runtime
list. This keeps unsupported automatic jobs off the game node while dedicated
signed game controls and node inventory continue to work.
Cloud/WorkForce visibility does not by itself assign a canonical Core mission,
grant native authority, or qualify full ecosystem execution.

Command claims and unacknowledged reports persist locally. Retrying report
delivery never reruns a game operation. Commands with a claim but no surviving
outcome remain unknown; the existing Cloud command lease decides their state.
Disconnecting does not kill a running game or remove worlds. Use the game's
normal Stop control before maintenance. This candidate is unsigned. Keep all
package files together and compare the published SHA-256 before running.

The bundled extractor is the publisher's 7-Zip 26.05 standalone 7zr executable,
stored as 7za.exe for the fixed adapter interface. Its exact publisher SHA-256 is
checked during packaging and again before extraction. Publisher release:
https://github.com/ip7z/7zip/releases/tag/26.05
The extractor license/provenance is in 7za.license.txt. No proprietary Minecraft,
FiveM, Java runtime, mod, server world, license key or account credential is
redistributed in this package.
