batocera-ops

# Batocera Ops Foundation for operating a Batocera cabinet with a coding agent over SSH. Read this first; the sibling skills (`batocera-roms`, `batocera-display`, `batocera-tuning`, `batocera-maintenance`) assume the connection pattern, path model, and safety doctrine defined here. ## Overview Batocera is an immutable-rootfs Linux distro for retro gaming. The system partition is **read-only**; everything you can change lives under `/userdata`. EmulationStation (ES) is the frontend; RetroArch and standalone emulators do the playing. Configuration is layered: a single `batocera.conf` holds most settings, but launch-time code (configgen) regenerates per-emulator configs on every launch, so hand-edits to the generated files get stomped. Getting these two facts right prevents most wasted sessions. ## Connecting Batocera defaults to password SSH (no key from a fresh client). Parameterize the host so nothing is hardcoded: ```bash export BATOCERA_HOST=192.168.1.50 # your cabinet's LAN IP ``` Batocera's **documented default credentials are `root` / `linux`.** If yours still uses them, change the password (ES menu → System Settings → Security, or `passwd` over SSH) — a machine you SSH into as root should not ship with a published password. The examples below read the password from an env var so it never lands in shell history or a committed file: ```bash export BATOCERA_PASS='linux' # replace with your actual password # convenience wrapper used throughout these skills SSHB...