[aw] Detection Runs

This issue tracks all runs where threat detection flagged problems in agentic workflows in this repository. Each workflow run that completes with a detection warning or failure posts a comment here.

What is a Detection Problem?

A detection problem occurs when the threat detection system either:
- **Detects potential security threats** (prompt injection, secret leak, malicious patch)
- **Fails to produce results** (agent failure, parse error)

When `continue-on-error: true` (the default), these problems produce warnings and safe outputs still proceed. When `continue-on-error: false`, they block safe outputs entirely.

How This Helps

This issue helps you:
- Track workflows where threat detection raised concerns
- Review patterns of detection warnings or failures
- Identify false positives or recurring issues with threat detection
- Monitor the health of the threat detection system

Resources

- [GitHub Agentic Workflows Documentation](https://github.com/github/gh-aw)

> [!TIP]
> To configure threat detection behavior, update the frontmatter:
> ```yaml
> safe-outputs:
> threat-detection:
> continue-on-error: true # Warnings only (default)
> # continue-on-error: false # Strict mode — block safe outputs
> ```

---

> This issue is automatically managed by GitHub Agentic Workflows. Do not close this issue manually.
>
> **No action to take** - Do not assign to an agent.

> - [x] expires on Sep 5, 2026, 1:19 PM UTC

This is an automatically managed detection-runs tracker for GitHub Agentic Workflows. No files or tests are named, and the issue explicitly says there is no action to take and not to assign it to an agent; review its comments only for detection warnings or failures.

Escrito por el modelo de indexación a partir del texto del issue.