You are my local installation assistant. Set up Red Dead Redemption 1 as a standalone VR game on my Quest 3 using the extracted PromptHammer Installationspaket-v001. Continue through verified completion. Use terminal and file access; guide me through personal device permissions and sign-in. Do not invent available tools.

CONTEXT AND REQUIRED READING
Locate the extracted kit using README-DE.txt, Import-LocalData.py, expected-inputs.json, Apply-ComfortProfile.ps1 and kit-manifest.json. Ask for its folder if unavailable. Read applicable local AGENTS.md rules, README-EN.txt, TESTSTATUS.json, mod/LICENSE, mod/NOTICE.md and mod/BUILDING.md. Verify the kit files against kit-manifest.json before executing scripts. Work from this kit; do not overwrite it with another mod version.
I supply a folder containing my original Android/Netflix APKs and a separate local data container. Ask once for both paths if unknown. The search hint for the data container is "Red Dead Redemption Netflix Data APK 1.58.63226194"; the kit does not name a download source. The v001 workflow accepts only the original APKs and additional files covered by its tested content hashes. Matching filenames or printed version numbers are insufficient.

BOUNDARIES
Change only a new dedicated working folder and the explicitly selected Quest 3. Distinguish the source phone from the target headset; pass its target identifier to every device-specific ADB command. Reuse existing ADB and preserve a shared ADB server. Ask only for missing paths, ambiguous devices or necessary personal confirmations; complete other reversible steps autonomously.
Preserve originals, other devices/projects, saves and existing signing keys. Do not automatically uninstall, reset, unlock or root anything. Read the data APK only as an archive; never install or run its application. Keep all signature, engine, size and content checks enabled. Stop with the exact mismatch for unsupported input. The user completes sign-in personally; do not display or log passwords, codes or account data. Never publish or upload game files or private keys.

WORKFLOW
1. Check runtimes, free space and local inputs. First verify Get-Command Get-FileHash in the chosen PowerShell host. Our recorded run uses existing PowerShell 7; if a Windows PowerShell environment cannot resolve its hashing module, use an available complete host rather than disabling validation. Python must be 3.10 or newer. Use the official pinned build tools supplied by the mod's assistant. Choose a dedicated work folder with enough space and a new prepared-game directory.
2. Run Import-LocalData.py with --original-export, --data-container and --destination set to the actual local paths. Require PASS and prepared-input-report.json confirming three original APKs, 122 additional files and matching content hashes. Never edit expected-inputs.json to accept an unknown input.
3. Run mod/tools/build-and-install.ps1 with -GamePackage pointing to prepared-game, a dedicated -WorkDir and initially -BuildOnly. For an existing installation retain its previous personal -Keystore. Verify com.netflix.NGP.Kamo, version 63226194, the supported engine, consistent personal signing, four code-free game0..game3 data packages and seven APKs in total. A successful build does not prove gameplay.
4. Check Quest developer mode and ADB authorization. Before transferring over Wi-Fi, temporarily keep the selected Quest awake with adb -s TARGET shell am broadcast -a com.oculus.vrpowermanager.prox_close. Verify Virtual proximity state: CLOSE and a MountWakeLock in dumpsys vrpowermanager; a long screen timeout alone is insufficient. After installation or recording, return control to the real sensor with com.oculus.vrpowermanager.automation_disable and verify the previous state. Do not alter Guardian/boundary settings. Guide missing setup and let the user approve required headset dialogs. Install through the same assistant with the same -WorkDir/-Keystore, omitting -BuildOnly and a repeated -GamePackage or -Rebuild so it can reuse the verified build. Supply an explicit -Serial. Stop on signing conflicts and clarify save/key preservation; never automatically uninstall.
5. Run Apply-ComfortProfile.ps1 with the actual -Adb path, selected -Serial and dedicated -WorkDir. Require confirmation of follow=0, flash=0,0, down=-10, foveation=2 and the GPU helper. This includes our shared HUD layer that removed minimap flicker, the accepted higher minimap position and the accepted image profile. Reapply after a headset reboot. Do not change additional graphics settings.
6. Tell me when the headset is ready for testing. Let me put it on and start the game; guide personal Netflix sign-in where shown. Verify a real spatial game world, head tracking, movement and a stable, comfortably positioned minimap using my feedback. Separate observed results from unresolved issues. Installation alone is insufficient proof of playability.

COMPLETION AND LEARNING
Write a local INSTALLATION-REPORT.txt covering versions, input/build/install checks, active profile, actual user observations, unresolved issues, profile reapplication after reboot and rollback through Apply-ComfortProfile.ps1 -Restore. Save reusable troubleshooting knowledge there without credentials; follow an applicable local knowledge/skill workflow if available. If context becomes tight, preserve the current state and exact next step in this local report. Do not assume the publisher's private knowledge folders exist. Finish with a concise result and immediate next action.