diff --git a/services/wolf.sh b/services/wolf.sh
index 58ceea2..7541b28 100644
--- a/services/wolf.sh
+++ b/services/wolf.sh
@@ -3445,7 +3445,7 @@ PYEOF
     echo "  4. First launch of each app downloads its container image."
     echo "     A black screen for ~60 s is normal."
     echo ""
-    echo "  Return to launcher:  Ctrl+Alt+Shift+W  or  START+UP+RB (controller)"
+    echo "  Return to launcher:  Ctrl+Alt+Shift+Q  or  Back/Select+Start+LB+RB together (controller)"
     echo ""
     echo "── PAIRING (the ./manage.sh pin workflow) ────────────"
     echo ""
@@ -3486,7 +3486,7 @@ PYEOF
     echo "  • Controllers auto-configure: ES-DE & RetroArch map Wolf's virtual pad"
     echo "    via SDL, no manual input setup needed"
     echo "  • Exit a game → ES-DE: Start+Select opens RetroArch menu → Quit,"
-    echo "    or the Wolf hotkey  START+UP+RB  /  Ctrl+Alt+Shift+W"
+    echo "    or the Moonlight hotkey  Back/Select+Start+LB+RB together  /  Ctrl+Alt+Shift+Q"
     echo "  • Add / refresh cores later:  ./manage.sh cores"
     echo ""
     echo "  Wolf's entire state folder lives on the game drive, so Steam games"
@@ -3681,7 +3681,11 @@ ES-DE is usable the moment you launch it; only ROMs and BIOS are yours to add.
   To remap inside ES-DE: Main menu → Input device settings → Configure
   keyboard and controllers.
 - **Exit a game** back to ES-DE: Start+Select opens the RetroArch menu → Quit,
-  or use the Wolf hotkey START+UP+RB (Ctrl+Alt+Shift+W on a keyboard).
+  or use Moonlight's own quit gesture — Back/Select+Start+LB+RB pressed
+  together on a controller (Ctrl+Alt+Shift+Q on a keyboard). This is a
+  Moonlight client feature, not something Wolf itself defines — confirmed
+  against Moonlight's own documented shortcuts after the previously listed
+  "START+UP+RB" / "Ctrl+Alt+Shift+W" turned out not to work at all.
 
 ## GameCube / Wii / PS2 — prefer RetroArch's own cores over standalone
 RetroArch's libretro cores (Dolphin for GameCube/Wii, PCSX2 for PS2) are
@@ -3761,6 +3765,34 @@ releases, auto-offered on install). Two things worth knowing:
 - Most retail Wii U games are encrypted and need your own Wii U common key
   (\`keys.txt\`) — Cemu's own First-Time Setup Wizard covers where that goes.
 
+**Controller and audio setup — do this from the Desktop app, not ES-DE.**
+Cemu's own Settings dialogs (Input Settings, General Settings) don't render
+correctly inside ES-DE's Sway kiosk session — buttons can be unreachable or
+invisible even though the dialog box itself shows up. They work fine from
+the **Desktop** (XFCE) app instead, and since Desktop shares the exact same
+\`~/.config/Cemu\` as ES-DE, whatever you configure there applies the next
+time Cemu launches from ES-DE too.
+
+1. Connect your controller to whichever device is running the **Moonlight
+   client** (not this server) before connecting.
+2. In Moonlight, connect to **Desktop**, open a terminal from its
+   application menu, and launch Cemu plain: \`~/Applications/Cemu-2.6-x86_64.AppImage\`
+3. Controller: **Options → Input Settings → Controller 1** → set Emulated
+   controller to **Wii U Pro Controller** → click **+** → API **SDL** →
+   select your controller from the list → use Cemu's own live
+   button-mapping screen to bind each button → save.
+4. Audio: **Options → General Settings → Audio** → set **TV** device to
+   your real output.
+5. If setting the TV device ever hangs Cemu outright (a real, reproducible
+   Linux Cubeb/PulseAudio stream-open stall, matches cemu-project/Cemu#601
+   upstream) — a full Wolf restart (\`sudo ./setup.sh wolf\` from this
+   repo, not just reconnecting) reliably cleared it in testing, giving a
+   fresh PulseAudio session to work with. Reconnect to a fresh Desktop
+   session afterward and try again.
+
+ROMs are mounted at \`/ROMs\` inside Desktop too, so Cemu's own File → Load
+can browse straight to \`/ROMs/wiiu/\` without needing ES-DE at all.
+
 ## TI-99/4A
 If you said yes to the TI-99/4A prompt during install, it's set up as a
 real ES-DE system (\`roms/ti994a/\`, artwork scraping, gameplay-time