Tuning: disable GNOME animations; document GPU governor tuning

Bazzite base already covers the rest (max_map_count, zram, gamemode,
tuned profiles); governor stock curve (1000-1850 MHz, 85C throttle)
left as-is — ceiling tuning is documented in OPERATIONS.md for after
on-hardware thermal testing.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

OPERATIONS.md

@@ -53,6 +53,18 @@ cat /sys/class/drm/card*/device/pp_dpm_sclk   # GPU clock scaling
 df -h /                                       # disk space
 ```
 
+## Tuning the GPU (optional, after thermal testing)
+
+The GPU governor's curve lives at
+`/etc/cyan-skillfish-governor-smu/config.toml`. Stock range is
+**1000–1850 MHz**, thermal throttle at 85 °C — a good default. If temps stay
+comfortably low during long sessions you can raise `max` under
+`[frequency-range]` (safe-points up to 2000 MHz are pre-defined; higher ones
+are in the file, commented out). Running hot or loud? Lower `max` to ~1500.
+After editing: `sudo systemctl restart cyan-skillfish-governor-smu`.
+There is also `cyan-skillfish-performance-mode` for temporarily pinning
+high clocks. Change one thing at a time and re-check `sensors`.
+
 ## Misc
 
 - Reboot: `sudo systemctl reboot` — Shutdown: `sudo systemctl poweroff`

files/console/etc/dconf/db/local.d/50-bc250-console

@@ -14,3 +14,7 @@ idle-delay=uint32 0
 [org/gnome/desktop/screensaver]
 lock-enabled=false
 idle-activation-enabled=false
+
+# Console-like snappiness: UI animations cost frames on this GPU
+[org/gnome/desktop/interface]
+enable-animations=false

files/console/usr/share/doc/bc250-console/OPERATIONS.md

@@ -53,6 +53,18 @@ cat /sys/class/drm/card*/device/pp_dpm_sclk   # GPU clock scaling
 df -h /                                       # disk space
 ```
 
+## Tuning the GPU (optional, after thermal testing)
+
+The GPU governor's curve lives at
+`/etc/cyan-skillfish-governor-smu/config.toml`. Stock range is
+**1000–1850 MHz**, thermal throttle at 85 °C — a good default. If temps stay
+comfortably low during long sessions you can raise `max` under
+`[frequency-range]` (safe-points up to 2000 MHz are pre-defined; higher ones
+are in the file, commented out). Running hot or loud? Lower `max` to ~1500.
+After editing: `sudo systemctl restart cyan-skillfish-governor-smu`.
+There is also `cyan-skillfish-performance-mode` for temporarily pinning
+high clocks. Change one thing at a time and re-check `sensors`.
+
 ## Misc
 
 - Reboot: `sudo systemctl reboot` — Shutdown: `sudo systemctl poweroff`