Here's what's possible: there are some alternative, command-line tools that get built (command-line puzzle solvers) but not installed. They're not part of the install rule. I could, for instance, bulid them for testing, but I get the sense that by the time the test function is called, access the the source is long gone.

Perhaps instead I should run said test during the install / build phase, and fail out if sanity tests fail.

(More [ignorable] details below.)
I spoke with Simon about his build process, and he basically pushes new releases ad-hoc (which means I'll occasionally update this rule with new urls for branches.) and his his automated tests are pretty limited. I may spend more time writing tests, but that remains to be seen.