Skip to content

[deep-report] Fix failure_kind driver_exit mistagging in safe-output health monitoring #50022

Description

@github-actions

Description

Across two consecutive Safe Output Health Monitor audits (2026-08-02 and 2026-08-03), 100% of confirmed in-scope safe_outputs job hard-failures were mistagged driver_exit at the run-summary level — implying an out-of-scope agent-container crash when the actual cause was a successful agent job followed by a failed safe_outputs job. On 2026-08-03, all 4/4 in-scope failures were mistagged; a consumer trusting the tag alone would report zero incidents instead of 4.

Expected Impact

Restores trust in the failure_kind field for automated and manual safe-output health monitoring — currently every audit has to manually Grep-sweep job_details[] for safe_outputs conclusions to get accurate numbers, which doesn't scale and is easy to skip.

Suggested Agent

Existing maintainer / owner of the run-summary/failure-kind classification logic

Estimated Effort

Medium (1-4 hours) — needs the summary generator to check job_details[].safe_outputs.conclusion before falling back to driver_exit for runs where the agent job itself succeeded.

Data Source

DeepReport Intelligence Briefing 2026-08-03, cross-referencing Safe Output Health Monitor discussion #49905.

Generated by 🔬 Deep Report · agent · 112.8 AIC · ⌖ 36.4 AIC · ⊞ 5.7K ·

  • expires on Aug 5, 2026, 7:43 AM UTC-08:00

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions