When an input moves mid-run, vx keeps the result and skips the save

vx handles inputs that move mid-run by keeping the result but skipping the save process. Because a cache key represents inputs at a specific moment, saving outputs from changed bytes would cause incorrect replays. vx notifies the user which file changed and requires declaring it in cache.outputs for saving. Similarly, Turborepo 2.11.7 computes task hashes before execution and uses save_outputs to store declared outputs under that hash after a successful run, regardless of mid-run changes.