Preserve Cache between the runs

We have large build targets (one for each top level directory) in https://github.com/harness/harness-core.

When I run gazelle - I have to deal (manually fix) with a bunch of cyclic dependencies. Each time I refactor, I run gazelle to regenerate the build files. Even if changes are isolated to a sub-directory, I have to run gazelle on entire workspace. It appears on each run, we map package to build target -- so if we try running gazelle only on a sub-directory, it does not resolve imports from other directories.

Is there a way to create a cache of such mapping and update it with new runs?

The issue names no files, tests, or entry points. Start by examining Gazelle's package-to-build-target mapping and how a sub-directory run discovers imports across the workspace. Done means a cache can preserve that mapping and be updated by later runs without requiring a full-workspace regeneration.

Written by the indexing model from the issue text.