[gh-aw-parity] gh-aw threat-detection changes to review - 2026-09-13

3 new gh-aw (pre)releases scanned (v0.89.8 → v0.89.10), 1 threat-detection-related change found.

## Releases
- v0.89.9 (prerelease, 2026-09-12) — https://github.com/github/gh-aw/releases/tag/v0.89.9

## Threat-detection changes
- [#60380](https://github.com/github/gh-aw/pull/60380) — Preserve zero-credit threat detection accounting — shipped in v0.89.9

## Why this matters
This repository ships the `threat-detect` binary consumed by `gh-aw`; changes like this may require matching updates here to stay in parity.

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

> Generated by [gh-aw Parity Monitor](https://github.com/github/gh-aw-threat-detection/actions/runs/34736725234) · copilot · auto · 21.4 AIC · ⌖ 4.21 AIC · ⊞ 9K · [◷](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-parity-monitor%22&type=issues)

Start by reading gh-aw PR #60380 and the local threat-detect implementation, then compare the shipped v0.89.9 behavior with this repository. Determine whether the zero-credit threat-detection accounting change requires a matching update here, and validate that the binary remains in parity with gh-aw.

Written by the indexing model from the issue text.