[gh-aw-issues] New gh-aw threat-detection issues - 2026-09-11

1 new `threat-detection` issue found in `github/gh-aw`; 1 of them is already closed.

## Issues

- [#50659](https://github.com/github/gh-aw/issues/50659) — threat-detection: GITHUB_STEP_SUMMARY is unwritable in the AWF sandbox, aborting the v0.4.0 detector with exit 2 — closed, opened 2026-08-05 by ``@davidslater``, labels: bug, high-priority, cookie

## Why this matters

This repository ships the `threat-detect` binary consumed by `gh-aw`, so these issues may require follow-up work here.

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

> Generated by [gh-aw Threat-Detection Issue Digest](https://github.com/github/gh-aw-threat-detection/actions/runs/34570617037) · copilot · auto · 26.2 AIC · ⌖ 6.42 AIC · ⊞ 9.4K · [◷](https://github.com/search?q=repo%3Agithub%2Fgh-aw-threat-detection+is%3Aissue+%22gh-aw-workflow-call-id%3A+github%2Fgh-aw-threat-detection%2Fgh-aw-issue-digest%22&type=issues)

Start by reading linked issue #50659 and checking whether its closed resolution requires a change to the threat-detect binary consumed by gh-aw. Confirm whether the GITHUB_STEP_SUMMARY failure in the AWF sandbox is already addressed; done means no follow-up here, or a separate actionable issue naming the affected entry point and test.

Written by the indexing model from the issue text.