[AW Top 10] 06 Investigate engine driver crashes before safe output #71074

Priority 6/10 | 4 source issues | Impact 4/5 | Confidence 2/5 | Effort 3/5

One assignment, one coherent fix

Several workflows fail with SDK driver errors or crashing driver steps before any terminal safe output is recorded.

Implementation scope

Capture the driver stderr and failing tool call into the failure report, find the shared SDK error, and fix it or add bounded retry for it, including the redact-secrets step exit.

Done when

• The driver error is reproduced or its cause documented with a regression test.
• Failure reports include the underlying driver error text.

Why now

The crash classification recurs across Contribution Check, Community Attribution, Azure Codex and the chronic redact step, but the shared cause is not yet proven.

Unchanged AW sources close only after this summary is completed. Newer source activity and not-planned retirement do not trigger source closure. Assigned summaries are frozen; unassign to allow reclustering.

Generated by AW Essential Issue Clustering · copilot · auto · 30.7 AIC · ⌖ 0.619 AIC · ⊞ 8.9K · ◷