App 2.42.0: music-sources check on the Logs tab

Before a now-playing display, find where the head unit tells what is
playing, read only: the players Android reports, the active media
sessions, and every media browser service with its song, CarPlay's
(com.allgo.remoteui.mediabrowserservice) among them. The report is saved
and sent like a signal recording (shared SignalRecorder.saveCopies).
Also the findings of the first two recordings from the server.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LhzAVaUyqcw5PkGjz4mWW6

.claude/skills/car-logs/SKILL.md

@@ -62,8 +62,18 @@ control's target speed (0.0 when only polled); `0x2140A15A` moved between 3 and
 times they name is a lead; say how sure it is, and that it is not confirmed until a second
 drive shows the same.
 
+## Music-sources checks
+
+`fetch-logs` also brings `media-probe-YYYYMMDD-HHMMSS.txt` (Logs tab, "Check music sources",
+`MediaProbe`). Three parts: audio players (use, app, state), active media sessions, and every
+media browser service with `connected` / `refused or failed` / `no answer`, then its state and
+song (TITLE, ARTIST, ALBUM, ALBUM_ART as a size). CarPlay's is
+`com.allgo.remoteui.mediabrowserservice/...RemoteUIMediaBrowserService`. Ask what was playing
+when the check ran.
+
 ## Rules
 
-- Recordings are the car's data: `logs/` and `/signal-recording-*.txt` are gitignored. Never
+- Recordings and checks are the car's data: `logs/`, `/signal-recording-*.txt` and
+  `/media-probe-*.txt` are gitignored. Never
   commit, publish or upload them anywhere.
 - Findings that change what the project knows go into a `SPECS.md` done-log entry, as usual.