Repository navigation
v1.8.2
Fixed
Auditor Session Detection Bug 馃敡
Fixed false 0/100 health scores caused by flawed session success/failure detection.
Root Cause:
- Success detection looked for narrow patterns (
"Successfully","PR created successfully") that didn't match actual log output ("SUCCESS","PR created:") - Failure detection was too broad (
'error' in content.lower()) catching false positives
Fix:
- Now detects actual success patterns:
": SUCCESS","PR created:",": ADDRESSED" - Now detects actual failure patterns:
"- ERROR -"(log level),": FAILED" - Sessions with neither clear success nor failure are not counted (e.g., no work to do)
This caused 100% session failure rate even when all sessions were successful, driving health scores to 0/100.