Firmwaredesk: Test Matrix

Firmwaredesk keeps a release-evidence matrix in which a test result only counts as current while the firmware artifact, the exact board unit, the case revision, and the recorded bench state all still match. Plan: import a firmware file to fingerprint it — SHA-256 is computed on the device, Intel HEX records are checksum-verified, UF2 blocks and family IDs are read — then describe your board units and write the test cases yourself. Boards carry a lineage: revising one keeps its history while separating old evidence from new hardware. Execute: at the bench, pick the board under test, mark each case Pass, Fail, Blocked, or Not run, and append the session. Editing a case bumps its revision and the plan revision; changing the fixture, power, or ambient state bumps the precondition revision. Each edit immediately flips the affected matrix cells to Stale or Missing, so the counts always tell…