Record issue 10 regression results and use the Windows fixture host

docs/windows-quick-test.txt

@@ -6,6 +6,8 @@ The package detects the real GPU automatically. Do not rename any DLLs.
 
 1. EXTRACT THE WHOLE ZIP to a normal writable folder, e.g. Desktop\d4r-test.
    Do not run it inside the ZIP. Do not copy files into the game manually.
+   Already installed an older test? Close the game and run RESTORE-GAME.cmd
+   from that old package first, then extract this version to a new folder.
 
 2. CLOSE YOUR GAME. Have these TWO ORIGINAL NVIDIA files ready:
    _nvngx.dll       version 32.0.16.1714

docs/windows-rdna4-port.md

@@ -67,6 +67,18 @@ standalone layout/error/coverage/RGB checks with:
 .\scripts\windows\test-ngx-feature-layout.ps1 -DiagnosticRoot .\dist\windows-gpu-coverage-gfx1201 -HipRoot .\.tools\therock-10.2.0a20260929\_rocm_sdk_core -ZludaRoot .\dist\zluda-windows-gpu-coverage -NativeRoot .\dist\windows-gpu-coverage-game-gfx1201\d4r\native -OptiScalerDll .\dist\optiscaler-windows-d4r\OptiScaler.dll -NgxCore .\_nvngx.dll -DlssDll .\nvngx_dlss.dll -OutputDirectory .\test-results\ngx-feature-layout
 ```
 
+The rebuilt compact installer passes six isolated Windows PowerShell 5
+fixtures (`quick-fixtures-final/summary.json`): exact backup/restore with the
+original game DLSS DLL preserved, automatic gfx1201 selection, a child that
+refuses debugging with empty stderr, and four negative input/package gates.
+The child exits normally with no debugger and is classified as inconclusive,
+with hardwareValidationCompleted=false. No installed game is changed by the
+fixtures. Run `test-windows-quick-test.ps1` with the package and the local DLL
+paths to reproduce them; it selects Windows PowerShell 5 when called from 7.
+The follow-up compact release is `windows-quick-test-20261002-issue10` in the
+fork, with all eleven targets and a separate exact GPL corresponding-source
+asset. Native network arithmetic and conservative scheduling are unchanged.
+
 These tests do not validate the reporter's gfx1200 kernels or game image.
 The local Cyberpunk EXE is `D:\Games\Cyberpunk 2077\bin\x64\Cyberpunk2077.exe`;
 it is located but is not launched or modified while the user is away.

scripts/windows/test-windows-quick-test.ps1

@@ -7,6 +7,15 @@ param(
     [string]$OutputDirectory
 )
 $ErrorActionPreference='Stop'
+if ($PSVersionTable.PSVersion.Major -ge 6) {
+    # The fixture uses the .NET Framework C# compiler; the shipped launcher
+    # also runs Windows PowerShell 5. PowerShell 7 cannot emit an EXE via Add-Type.
+    $arguments=@('-NoProfile','-STA','-ExecutionPolicy','Bypass','-File',$PSCommandPath,
+        '-PackageRoot',$PackageRoot,'-NgxCore',$NgxCore,'-DlssDll',$DlssDll)
+    if ($OutputDirectory) { $arguments+=@('-OutputDirectory',$OutputDirectory) }
+    & "$env:SystemRoot/System32/WindowsPowerShell/v1.0/powershell.exe" @arguments
+    exit $LASTEXITCODE
+}
 $repo=[IO.Path]::GetFullPath((Join-Path $PSScriptRoot '../..'))
 $PackageRoot=(Get-Item -LiteralPath $PackageRoot).FullName
 if (!$OutputDirectory) { $OutputDirectory=Join-Path $repo ('test-results/windows-quick-test/'+(Get-Date -Format 'yyyyMMdd-HHmmss-fff')) }