Files
PS5_RetroArch/docs
Mihawk 7dd9b5d198 Prove the Option 1 baseline on the console
The vendored recipe's RetroArch payload now has a verified console run: it was
started through the console's homebrew launcher, the menu came up, and the
frontend wrote its own configuration tree beside the payload while it ran.

New tools:
- tools/console-launch.sh starts the title through websrv's /hbldr endpoint with
  the arguments and environment title/homebrew.js declares, and captures the
  payload's output. It prints what it is about to do before doing it, because
  the console is shared with the PS5_Vulkan session and every launch is asked
  for first (docs/DEPLOYMENT.md).
- tools/evidence.py distil turns a raw capture into a committed record plus the
  expectation it is checked against; compare replays every capture offline and
  exits non-zero on a difference.

Evidence: evidence/m1-baseline-loads/ (capture.json, expectation.json) replays
clean - "1 capture(s) replayed, 0 failed". The run's identity from the console's
control payload: app=24600 pid=151 under the homebrew title. The raw capture is
klog/launch-20260918-120546.log. The owner confirmed the menu was on screen.

Recorded as known-benign, with its exact text: the fontconfig error this build
prints before any driver starts. It is not a failure and the menu renders
anyway (docs/TROUBLESHOOTING.md).

Open and recorded as such: the deployed folder no longer lists retroarch.elf
although it was verified on upload and is what the run started; to re-check when
the console is next free.
2026-09-18 12:08:41 -04:00
..