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

Scanned 3 new gh-aw (pre)releases (v0.89.1–v0.89.3); found 1 threat-detection-related change.

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

## Threat-detection changes
- [#59740](https://github.com/github/gh-aw/pull/59740) — [ci-coach] Fix compiler-threat-detection-spec.md section numbering to restore TestFormal_* conformance — shipped in v0.89.1

## Why this matters
This repository ships the `threat-detect` binary consumed by `gh-aw`; changes to gh-aw's threat-detection-related spec/tooling may require matching updates here to stay in parity.

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

> Generated by [gh-aw Parity Monitor](https://github.com/github/gh-aw-threat-detection/actions/runs/34560364780) · copilot · auto · 26.5 AIC · ⌖ 4.89 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 pull request #59740 and the v0.89.1 release notes, then inspect how this repository's threat-detect binary relates to the changed threat-detection specification. Determine whether a matching update is needed and verify that parity with gh-aw is restored; the issue does not name files or tests to run.

Written by the indexing model from the issue text.