Does dagger/hilt KSP actually support incremental symbol processing? It seems changing any java or kotlin file in our project, even one that seemingly shouldn't contribute to the output, causes the ksp to re-run completely.
Analyzing the KSP log files kspDirtySet.log and kspSourceToOutputs.log turns out most of the times the files considered dirty are only used to produce some proguard rules. There are a lot of entries ending _HiltModules_KeyModule_LazyClassKeys.pro. Feels like something that could be skipped when minification is disabled.