A machine that cannot run `git` now gets one line of explanation instead of a stack trace. Every loop-engine and loop-cohort command needs git to confirm the spec directory sits inside your repository. When git could not be run at all — not installed, or a PATH entry shadowing it with something unexecutable — the command ended in a 33-line Python trace that also printed internal file paths, more output than a whole successful run of the loop. Both tools now answer that situation the same way, in one line.