review-debug

You can find ungated debug logging by auditing diagnostic outputs like FileAppend, FileOpen, and Tooltip writes to ensure they are wrapped in configuration checks. This identifies unguarded disk writes and missing logging coverage on failure paths that cause production overhead.

Debug logging coverage gap analysis identifies failure paths and error conditions lacking diagnostic logs. You need this when missing context hinders debugging efforts, ensuring critical diagnostic-worthy events are captured while preventing ungated disk write overhead in production.

You audit diagnostic output for overhead by tracing FileAppend and FileOpen calls to verify configuration check wrappers. This validates findings against codebase evidence and call chains, ensuring diagnostic writes do not execute unless explicitly enabled in production.

Yes, you can use parallel exploration agents to audit independent code areas for logging issues. This systematically isolates ungated diagnostic writes and coverage gaps, requiring validation of all findings against codebase evidence and call chains for accuracy.

Auditing debug logging without checking call chains risks false positives for ungated FileAppend or Tooltip writes. Validation against codebase evidence is required to confirm whether diagnostic outputs are properly gated by upstream configuration checks before reaching production.