It helps, but it’s important to have a name and a green check mark for each result so people understand WHY the magic doesn’t permit them to use the machine.

Yep, this is good. On one occasion, I saved myself a huge amount of back and forth by writing a dumb "test suite" for a software artifact to be shipped to a client; i.e. make sure it was compressed as a zipfile; it included an INSTALL.md; it was installable via [specific installer program]; it included [specific runtime libraries versions]; etc. etc.

Turns out human software engineers are really bad at fulfilling even well-specified requirements, so you will always save time by automating as much of the conformance testing as possible.