[aw-failures] [aw-fix] P1: report_incomplete safe output rejected — "Missing required field: workflow_name" #46376

Fix the report_incomplete payload — it omits the required workflow_name, so the safe output is rejected and the incomplete-run report is silently dropped.

Affected workflow / run

• Daily Firewall Logs Collector and Reporter — run 29628356788 (2026-07-18, schedule)
• safe_outputs job error: ✗ Message 3 (create_report_incomplete_issue) failed: Missing required field: workflow_name → 1 safe output(s) failed

Impact

When an agent emits report_incomplete, the create_report_incomplete_issue handler validates the payload and hard-fails on a missing workflow_name. The failure notification is never filed and the safe_outputs job goes red — masking the real incompleteness signal instead of surfacing it.

Probable root cause

The report_incomplete payload emitted via the safeoutputs CLI (or assembled by the compiler) does not populate workflow_name, while the handler/schema treats it as required. Either the emitter must inject workflow_name from workflow context at emit time, or the handler must default it.

Proposed remediation

• Inject workflow_name (from GITHUB_WORKFLOW/workflow context) when emitting report_incomplete, or
• Make workflow_name optional in create_report_incomplete_issue and fall back to the workflow context server-side.
• Add a compile/validation test asserting every report_incomplete payload carries workflow_name.

Success criteria

• A workflow emitting report_incomplete produces an accepted safe output and a filed incomplete-run issue.
• safe_outputs passes on the Daily Firewall Logs Collector schedule.
• Regression test covers the missing-field path.

Generated by 🔍 [aw] Failure Investigator (6h) · 186.2 AIC · ⌖ 41.5 AIC · ⊞ 5.2K · ◷

• expires on Jul 24, 2026, 11:32 PM UTC-08:00