docs: Payload Guest crashes — never use it for orbisRPC

AGENTS.md

@@ -33,7 +33,7 @@ Beta Discord Rich Presence daemon for jailbroken PS4. Testers install the
 - Docs: tester flow in `README.md`, reference in `docs/`
   (`TROUBLESHOOTING.md`, `CONFIG.md`, `BUILDING.md`), hardware research in
   `docs/research/`. Keep them in sync with behavior changes.
-- Don't tell testers to use Payload Guest for orbisRPC; autorun via
+- Never tell testers to use Payload Guest for orbisRPC — it crashes. Autorun via
   `/data/payloads` is not recommended on test builds.
 - License is undecided (MIT vs GPL). Don't add GPL code or a LICENSE
   file until the owners pick.

docs/INSTALLER.md

@@ -20,7 +20,7 @@ reads like a verdict on Discord itself. The daemon reports real reachability
 in its own log once started.
 
 The installer never boots anything directly. Starting the daemon is
-Payload Guest's `/data/payloads/` directory — pick `evict.elf` first
+the `/data/payloads/` directory — pick `evict.elf` first
 (removes old orbisrpc instance), then pick `orbisrpc.bin`.
 No loopback ports, no injection, no boot proof to go wrong.
 
@@ -67,7 +67,7 @@ button on No, which inverts the whole wizard.
 
 ## Auto-start
 
-Payload Guest AutoRun: enable it for `orbisrpc` once and the daemon
+GoldHEN AutoRun: enable it for `orbisrpc` once and the daemon
 starts on every jailbreak. The queue is menu-managed; the installer
 shows where, it can't write the queue itself.
 

docs/TROUBLESHOOTING.md

@@ -66,7 +66,8 @@ Never share the config file — a user token is full account access.
 ## Payload won't start
 
 - The payload lives at `/data/payloads/` — put the `.elf` there (FTP/USB)
-  and launch it from the payload list. Don't use Payload Guest for orbisRPC.
+  and launch it from the payload list. Never use Payload Guest for
+  orbisRPC — it crashes.
 - No sender handy? elfldr (port 9021) or the BinLoader server (port 9020)
   also work — see [`injecting.md`](injecting.md).
 - Ports closed? GoldHEN's BinLoader toggle is off, or the console