v0.5.17 - Treat a lost runner's notice as explaining a job with no log in failure triage (#943)

🌟 Summary

Release v0.5.17 improves CI failure triage so lost-runner failures can be correctly identified as transient and automatically rerun.

📊 Key Changes

• 🤖 Updated the triage guidance to treat GitHub’s notice that a runner lost communication as an explanation for a job that has no log.
• ✅ In replay tests of one affected run, triage classified the failure as Transient in all 65 trials, compared with 60 of 65 before the change.

🎯 Purpose & Impact

• 🔄 Repositories using automatic reruns are less likely to miss a retry when a runner disconnects before producing logs.
• 🧭 The change resolves a conflict in the triage instructions: missing logs generally mean Unclear, but a lost-runner notice provides a specific reason to treat the failure as Transient.
• 🛠️ No model or user-facing feature changes are included; this release focuses on more reliable CI failure handling.

What's Changed

• Treat a lost runner's notice as explaining a job with no log in failure triage by @glenn-jocher in #943

Full Changelog: v0.5.16...v0.5.17