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

Scanned 2 new gh-aw (pre)releases (v0.88.5..v0.88.6); found 1 threat-detection-related change.

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

## Threat-detection changes
- [#58607](https://github.com/github/gh-aw/pull/58607) — Warn when Pi threat detection lacks Copilot authentication — shipped in v0.88.5

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

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

> Generated by [gh-aw Parity Monitor](https://github.com/github/gh-aw-threat-detection/actions/runs/34185267430) · copilot · auto · 31.1 AIC · ⌖ 7.39 AIC · ⊞ 10K · [◷](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 upstream PR #58607 and the v0.88.5 release notes, then inspect the repository's Go implementation of the threat-detect binary to compare behavior. Done means determining whether the authentication warning needs a parity change here and recording or implementing the resulting update.

Written by the indexing model from the issue text.