Find Non-Lambda Log Calls Overview Two related logging hygiene issues: 1. Lambda overload missing. calls that use string interpolation without the lambda overload waste string allocation when the log level is filtered out in release builds. 2. Throwable dropped in catch blocks. calls inside blocks that interpolate but don't pass lose the stack trace, and log nothing useful when is null (NPE, IOException with no message, etc.). When to Use - After merging branches that add new logging - Periodic audit of logging hygiene - After migrating usages to the shared wrapper What to Flag Calls with str…