👍🏼 logic looks sound. Verified this fixes #1323 locally as well.

This is a fix for a single symptom of a larger issue. It solves for the fact that our method of moving logs into the cache is:

1. Write the log file into the package directory at a consistent location (e.g. examples/basic/apps/docs/.turbo/turbo-build.log)
2. Add the path to the package outputs.
3. Move all the contents into the cache via hardlinks.

On a second run of the same task, since the file is in a consistent location, it writes the log to the same path which is hardlinked to an existing cache. This issue will show up every time.

This issue is just an instance of a larger problem we encounter with using hardlinks. Any time time a task is re-run and the task itself does not, say, remove the paths that it outputs to first (breaking the hardlinks on our behalf) it can pollute any number of previous local caches when writing to the same output paths.

I don't believe that trying to play whack-a-mole with breaking hardlinks is a sustainable solution. Even if we properly break hardlinks in our own code that doesn't preclude a user accidentally polluting their cache by modifying something manually.

Given that, I don't believe that we should take this approach to solving the problem. I have opened #1354 with an alternate proposal which I believe addresses the root of the problem with the smallest possible change.