HydraUnrealEngine v1.3.0 now defaults UI, API and CLI packaging to Both (Win64 + Linux). Explicit single targets remain supported. All selected prerequisites are checked before compiling; targets build sequentially into separate fresh archives and each gets its own ZIP, public download URL and SHA256. Overall success requires all targets. Earlier downloads and local package paths remain visible when a later target/upload fails or cancellation occurs. The existing explicit single-target CLI output-path contract is preserved. The optional remote dashboard's old singular URL field is unchanged; both results are exposed by the local UI/API.
Tool source 7623366, final publication/validation documentation 8a8da72, committed/pushed:
https://github.com/cederikdotcom/hydraunrealengine/blob/master/docs/runbooks/runbook.md
Release CI passed tests/vet, web/UAT race tests, Windows build and publication:
https://github.com/cederikdotcom/hydraunrealengine/actions/runs/35024710193
Public latest.json reports1.3.0; full 15886336-byte executable download matches SHA256 567f9340d02e2d26bc0f4116f5d6cbedcb8b4a7f5f237fd0f6bea1c4796c3161.
Tests exercise default/single selection, Linux prerequisites before any Windows build, sequential independent archives, second-target failure, cancellation between targets, and separate real ZIP/chunked HTTP uploads of fixture packages with checksum/content isolation. Upload failure preserves the completed Windows link and Linux local output without a false overall success. Package and two-artifact job browser views inspected; the job view used fixture downloads.
On Fluffy, downloaded and checksum-verified v1.3.0. Its CLI reports Both by default. Omitting --platform correctly rejected the host's UE5.7.4 before any Windows compilation/output creation. This was a guard test: an actual dual Unreal cook on the required UE5.7.3 is not yet verified. Previous actual Windows cooking used5.7.4. Linux baseline, original Blueprint/OpenXR #636 and WiVRn #741 acceptance are unchanged; both validation issues remain open.
HydraMancer v0.3.2 source5c9c220 is deployed at https://hydramancer.experiencenet.com/experience . Three-step guide now says keep Windows + Linux (default), package/upload, share both links; single-target selection remains optional. Existing access behavior preserved.
Portal CI passed both binary and amd64/arm64 OCI release jobs:
https://github.com/cederikdotcom/hydramancer/actions/runs/35024724500
Reviewed HydraSkin dry run and applied v0.3.2 on pi004/node-50ab5309. Runtime/image agree; recorded digest matches published manifest index:
sha256:b435d99b77a8952c3266bb1046fb9bc1e555ef56c9a44bd23679d71bd6947a39
Persistent state/proxy devices preserved; auto-update off. Public/mesh health and default plus both legacy platform routes passed; public mobile page inspected. Portal completion documentation: 5f3a0f2 (committed/pushed), https://github.com/cederikdotcom/hydramancer/blob/master/docs/runbooks/runbook.md.
No existing body session, experience-library entry, WiVRn runtime, engine installation or dedicated Perforce configuration was changed. Fluffy received only the isolated release/guard evidence under C:\Builds\HydraUnrealToolValidation\20260915-v130. Own local preview processes stopped.
Original scope follows.
User request, 2026-09-15: support both targets and provide both by default. Default UI, API and CLI packaging to Windows + Linux, retain explicit single-platform choices. Run target builds sequentially with separate archives/downloads and checksums. Validate prerequisites for all requested targets before building; never label a partial result as complete. Preserve completed artifacts if the other target fails or cancellation occurs. Update the simple HydraMancer guide, release the Windows tool and deploy the portal image. Acceptance: meaningful dual-target sequencing/isolation/failure/cancellation and UI/API tests, CI, publication and public checks. Existing UE5.7.3 Linux baseline and WiVRn acceptance remain unchanged; document live validation limits.