Are there details about how caching works in pants? Specifically, this answer I'm trying to answer: 1. Under what conditions are PEX files built and why? I've found that if I am using a remote cache and build against a particular git commit (i.e. abc) and then if I wipe out the cache and rebuild again it cancels the build and successfully pulls from the remote cache (as you would expect). I've followed https://www.pantsbuild.org/blog/2022/08/02/optimizing-python-docker-deploys-using-pants; when I wipe out the cache and modify just a first party source file and make a new commit (i.e. xyz) I would expect it to pull the pex deps binary from cache instead of rebuilding it (because 3rd party deps haven't changed), but what I find is that it doesn't do this -- pants rebuilds the deps binary pex. I'm trying to understand why so that I can improve the efficiency of my build.