🤖 Proto Rig firmware version stays at 1.8.0 after successful update/reboot

## Summary

Proto Rig firmware update appears to complete successfully in Proto Fleet, but the miner's displayed firmware version does not change afterward.

## Steps to reproduce

1. Start with a Proto Rig miner on firmware version `1.8.0`.
2. Upload a firmware file in Proto Fleet that targets the Proto Rig.
3. Trigger the firmware update from the miner actions menu.
4. Wait for the update flow to complete.
5. Wait for the miner to reboot and return to `Hashing`.
6. Check the firmware version shown for the miner in Proto Fleet.

## Expected behavior

After the update completes and the miner returns to `Hashing`, the displayed firmware version should change to the updated version (2.4.6 in the example).

## Actual behavior

The update completes, the miner reboots, and the miner returns to `Hashing`, but the displayed firmware version remains `1.8.0`.

## Version / environment

- Detected on Friday, August 14, 2026.
- Proto Fleet version under test: local RC manual-test environment from `v0.2.10-rc.5`.
- Environment: local `fleetnode-ui-test` stack on macOS.

## Notes

- Reproduced during local manual testing on Friday, August 14, 2026.
- This report is specifically about the firmware version remaining stale after a successful-looking update/reboot flow.
- Screen recording added:

https://github.com/user-attachments/assets/cc3a805d-7b42-4b71-869c-d71e6859cddf

Reproduce the firmware update in the local fleetnode-ui-test stack, following the miner actions menu through reboot and return to Hashing. Trace where Proto Fleet reads and displays the miner firmware version after the update, then verify that the displayed version changes from 1.8.0 to the updated version, such as 2.4.6.

Written by the indexing model from the issue text.