Add wacky function to extract dependency coords from task output

Works surprisingly well, though we still have to map the coords
to local cache (and deal with aars...?)