A camera-control project found a small reporting bug with a large consequence: its acceptance report named the Raspberry Pi model when hardware was detected, but said nothing when the test ran elsewhere. A reader could mistake that silence for a hardware-backed pass. The harness now prints either the real model or HARDWARE: NOT DETECTED in every result.
The code computes hardware status once and repeats it in the environment block, the copyable result record, and the final result. A regression test requires the status to remain explicit. That turns the machine used for a test into checked evidence instead of optional context supplied by the operator.
Any embedded test report that can pass on a developer computer and on a target board needs the same field. Add an assertion for target identity to the report format, then make a missing identity fail the hardware-qualified job. Otherwise a green software run can quietly enter the release record as proof that nobody collected.