Name the panel firmware in run logs: map inventory CRC fingerprints to firmware versions #236

Priority: low (nice to have; the data is already recorded).

What

Since the panel-inventory feature (#233, Studio v0.93), every run log's run_metadata.panels.firmware groups the panels by a fingerprint: a CRC32 over the first 64 KiB of each panel's running image, e.g. {"crc32": "0x9BE0D3C7", "panels": [1…20]}. That fingerprint is exact but not human-readable. Today you have to match it by hand against the images in flasher/firmware/. On 2026-09-29, 0x9BE0D3C7 turned out to be g6-panel-v0.3.1-isp-eintlow-9014b5b.

Proposal

• Look each fingerprint up in the flasher's firmware catalog, with the fingerprint computed the same way (CRC32 of the image's first 64 KiB). Sources are the in-repo flasher/firmware/* images and the remote Pages manifest the flasher already merges.
• Record the name next to the checksum in run_metadata.panels.firmware[], e.g. "name": "v0.3.1-isp-eintlow-9014b5b", and leave it null when unknown. Show it in Console → Panel firmware → Inventory.
• Consider precomputing the fingerprints into the manifest, so the Studio doesn't have to fetch whole images.

Done when

A run log and the Inventory panel name the panel firmware (or say "unknown image") without anyone matching checksums by hand.

🤖 Generated with Claude Code