Merge PR #2 from darthcircuit: Quest 1 support

Adds the modernQuest and quest1 headset flavours (Kryo CPU target, direct-VR
library entry on Quest 1), records the CPU target in the game kit and checks
it wherever a kit or game package is used, and gates the Quest 1 EFB-copy and
pipeline-scheduling workarounds on the monterey device.

Resolved docs/quest-port.md by keeping both sides: the foveated rendering
section and the Quest 1 renderer compatibility section, and both Build-Quest.ps1
command lines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/quest-port.md

@@ -182,6 +182,46 @@ density map does not reduce (the stores stay full size for non-subsampled images
 stays off by default; it pays only when `render_scale` makes the eyes pixel-bound, as at 1.3 on
 Luigi Circuit.
 
+### Quest 1 renderer compatibility
+
+Quest 1 identifies itself as Android device `monterey` and uses an Adreno 540
+driver that misrenders Aurora's general filtered EFB-copy shader. On that
+device, `GXCopyDisp` keeps the destination equal to the resolved EFB region so
+WebGPU can use `CopyTextureToTexture`; the later presentation pass still scales
+the result. Live RGB5A3 menu copies use a minimal RGBA passthrough shader for
+the same reason. Other Android devices retain the normal filtered and
+format-converting paths.
+
+Quest 1 must be built with the `quest1` flavour (`Build-Quest.ps1 -Headset
+quest1`). It targets the Snapdragon 835's Kryo CPU; the modern flavour targets
+`cortex-a77`, whose instructions can terminate the game with `SIGILL` on Quest
+1. Each variant's exported game kit records this CPU target, and the APK build,
+PC game build, on-headset build and package import all verify it. This prevents
+a kit left by another flavour from producing a library that can crash with
+`SIGILL`.
+
+The final Quest 1 firmware also cannot reliably promote this app's 2D setup
+panel into an immersive activity. Its APK therefore exposes two library
+entries: **WiiCompiled VR** starts the game directly in VR, while
+**WiiCompiled Settings** opens the setup/settings panel. After changing a
+setting, close the panel and start WiiCompiled VR from the library. The Play
+button in the settings panel explains this limitation instead of opening a
+black panel. Modern Quest builds keep the normal single launcher, whose Play
+button starts VR directly.
+
+The workaround was isolated on a physical Quest 1: it changed the boot/menu
+output from flickering black or white frames to a complete menu with character
+and vehicle previews. It does intentionally skip Wii-era RGB5A3 quantization on
+that device.
+
+Pipeline compilation is also scheduled differently on Quest 1. Its Adreno
+serializes much of `vkCreateGraphicsPipelines`, so a large equal-priority worker
+pool starved the translated game and OpenXR pacing threads without shortening
+the compile materially. Quest 1 uses two nice-level 5 workers and does not
+prewarm cached recipes in the background; a cached recipe is promoted and its
+workers are awakened when the game first requests it. Newer Android headsets
+and desktop retain the normal worker pool and prewarm behavior.
+
 ### Controllers
 
 Quest Touch controllers are not HID gamepads, so `openxr_input.cpp` syncs an
@@ -772,7 +812,10 @@ Android facts this design rests on, all measured on a Quest 3:
   also learned `--target-os windows|macos|linux|android` for
   `generate-data-init` and `translate-mod`, for pipelines that generate on
   another host.
-- `android/`: the Gradle project, one app with no flavours.
+- `android/`: the Gradle project, with `modernQuest` (the default script
+  target) and `quest1` headset flavours. They share the application ID and
+  storage, but select the appropriate CPU baseline, supported-device manifest,
+  and launcher behavior.
   `app/src/main/cpp/CMakeLists.txt` adds the repository's `runtime/` as a
   subdirectory with those Android choices and builds both game kit probes
   (the Retro Rewind one only when the translation includes the mod), which
@@ -794,8 +837,10 @@ installer's `BuildWorkspace/generated`, produced by the normal Windows pipeline)
 ```powershell
 powershell -ExecutionPolicy Bypass -File android/Prepare-QuestDependencies.ps1        # SDL3 3.4.4 AAR into android/app/libs
 powershell -ExecutionPolicy Bypass -File android/Build-Quest.ps1 -Install             # the app, its game kit and toolchain, debug-signed (the first run also builds Dawn from source)
+powershell -ExecutionPolicy Bypass -File android/Build-Quest.ps1 -Headset quest1 -Install  # Quest 1: Kryo CPU and direct-VR library entry
 powershell -ExecutionPolicy Bypass -File android/Build-QuestGame.ps1 -Install         # your game, against that kit, into Import (or WheelWizard VR's Build for Quest)
 powershell -ExecutionPolicy Bypass -File android/Build-QuestGame.ps1 -Product retro_rewind -Mod <RetroRewind6> -Install  # the mod and its pack (needs translate-mod output with --retro-wfc-payload)
+powershell -ExecutionPolicy Bypass -File android/Build-QuestGame.ps1 -Headset quest1 -Install  # game package from the Quest 1 kit
 adb push MarioKart.iso /sdcard/Download/                                               # then Select disc image in the launcher
 ```