[detection-failures] Detection failures in github/gh-aw - 2026-08-29

1 failing detection job found (0 hard failures, 1 soft failure) in the last 24 hours.

## Failing Detection Jobs
- Issue Monster — run https://github.com/github/gh-aw/actions/runs/33228870894 — job https://github.com/github/gh-aw/actions/runs/33228870894/job/99038183217 — success — step — engine failure: `reason=invalid_report_exhausted`, result file not found, no parseable verdict produced

```json
[
{
"workflow": "Issue Monster",
"run_id": 33228870894,
"run_url": "https://github.com/github/gh-aw/actions/runs/33228870894",
"job_id": 99038183217,
"job_url": "https://github.com/github/gh-aw/actions/runs/33228870894/job/99038183217",
"conclusion": "success",
"failure_kind": "step",
"reason": "reason=invalid_report_exhausted; ERR_PARSE: detection result file not found"
}
]
```

Scanned: https://github.com/github/gh-aw-threat-detection/actions/runs/33229201340

> Generated by [Detection Failure Monitor](https://github.com/github/gh-aw-threat-detection/actions/runs/33229201340) · copilot · auto · 188.4 AIC · ⌖ 5.64 AIC · ⊞ 10.1K · [◷](https://github.com/search?q=repo%3Agithub%2Fgh-aw-threat-detection+is%3Aissue+%22gh-aw-workflow-call-id%3A+github%2Fgh-aw-threat-detection%2Fdetection-failure-monitor%22&type=issues)

Start with the linked Issue Monster workflow run and job, then inspect the detection-failure monitor run that generated this issue. Trace why the result file was not produced or found and verify the workflow emits a parseable detection verdict without reporting a false success.

Written by the indexing model from the issue text.