trackActionInputs

When true (default after cascading), STIG runs the native Bazel target and fingerprints the C++ compile-action inputs from Bazel aquery. Source-code-analysis tasks consume that fingerprint, so changes in headers, generated files, BUILD graph inputs, command lines, or selected source files invalidate stale analysis outputs without hand-maintained Gradle source lists.

Set to false only for fast/offline/degraded runs where the native Bazel build cannot be executed or should not participate in invalidating STIG analysis. In that mode STIG writes a stable disabled fingerprint; existing compile-command outputs may still be reused, but native source changes are not tracked.