nx_boot_uefi_ramsize.nx

nx_boot_uefi_ramsize.nx -- NOS-R0.3: DISPLAY a discovered hardware value (the RAM map size). Extends R0.2 (the GetMemoryMap call): after calling BootServices->GetMemoryMap, the emitted EFI app now READS the returned MapSize and PRINTS it as hex -- the first rung that shows a real hardware value the OS discovered from the machine. This unlocks an installer UI ("this box has N bytes of RAM, install here"). The hex render is a real LOOP in machine code (8 nibbles MSB first, shr-by-CL + cmp + jcc), which is exactly why the exec-harness grew loop support. Entry ABI (MS x64): RCX=ImageHandle, RDX=SystemTable*. RSI=SystemTable, RDI=ConOut, RBX=hex write pointer (all callee-saved across the firmware call). Prints "RAM:0x" + 8 hex digits + CRLF. GetMemoryMap writes the required map size into *MapSize; we load it and format it. Scratch + hex buffer live in an RWX section (firmware writes MapSize; we write the hex chars). Build (sovereign): ./_offc/nx_sov_build_run.elf nx_boot_uefi_ramsize (nx_cc->nxasm, no gcc) Exec-proof: nx_emu_uefi runs it (GetMemoryMap hook returns 0x1800) -> expect "RAM:0x00001800". Self-gate: byte-reproducible + structural (subsystem=10, entry, GetMemoryMap call opcodes, the shr-by-CL hex-loop opcode present) + tamper (subsystem->3 rejects). Sovereign: syscalls only, no gcc/.sh. license_tier: ORIGINAL