DKR-R 1.0.8 - Windows startup memory correction

Both supplied 1.0.7 logs stop immediately after runtime-thread-started with
"Failed to allocate memory!" and runtime-error. Neither reaches RT64 setup.
Both logs have two code packages active, so they are not themselves a mods-off
comparison. The owner reports the same failure with mods disabled.

The only matching failure message is librecomp's RDRAM allocation path.
Its constants request a 4 GiB address reservation and 512 MiB accessible RDRAM.
The old Windows path committed all 4 GiB as PAGE_NOACCESS, then changed only
512 MiB to READWRITE. NOACCESS is protection, not an exemption from commit
charge. Microsoft documents MEM_COMMIT as charged against RAM/page files.
https://learn.microsoft.com/en-us/windows/win32/api/memoryapi/nf-memoryapi-virtualalloc

Reserve 4 GiB as NOACCESS, commit only the existing 512 MiB as READWRITE.
The remaining 3.5 GiB stays inaccessible and uncommitted. No address masking,
guest heap size, ROM, mod memory policy, graphics quality or save data changes.
Commit charge is reduced by 3.5 GiB per running Windows game instance.
Reservation/commit failure is logged with phase, immediate GetLastError,
requested sizes and availability. A failed commit releases the reservation;
the existing normal teardown still releases the complete range once.

The old logs contain no Windows error number, so they cannot prove the remote
PC's RAM, page-file configuration or exact OS rejection. This fixes a confirmed
unnecessary allocation; genuine exhaustion can still fail with useful details.
POSIX mmap/mprotect paths remain unchanged. All dependency changes are staged
build copies only. Protected dependency/generated guest trees stay untouched.

No game, launcher, mod, unit suite or benchmark is run by this pipeline.
Owner checks on the affected PC remain the final startup confirmation.
