AI Code Healer: Fixing Broken CI/CD Builds Without the Log Archaeology

It's Friday evening. Your pipeline goes red ten minutes after you pushed what felt like a safe change. The build log is 4,000 lines. You scroll to the bottom, grep for "error", find three candidates, none of which immediately explain the failure. Forty minutes later, you've traced it back to a transitive dependency that bumped a minor version upstream. That forty minutes is the problem. Not the bug, the diagnosis. CI/CD pipelines fail constantly in active codebases. The failure itself is usual...