[aw] Runtime Failure Observer (xharness) is missing required data

### Workflow Failure

**Workflow:** [Runtime Failure Observer (xharness)](https://github.com/dotnet/xharness/blob/main/.github/workflows/runtime-failure-observer.agent.md)
**Branch:** main
**Run:** https://github.com/dotnet/xharness/actions/runs/33031694972

> [!WARNING]
> **Missing Data Reported**: The agent reported missing data during execution.

**Missing Data:**
- **Helix job identifiers**: The required Send to Helix task logs for runtime build 1567845 contained no \`Sent Helix Job: <GUID>\` evidence, so Helix work items and xharness console failures cannot be identified.
- *Context*: Validated platform submission logs 723, 652, 535, 619, 698, 589, and 504 for the selected failed build.
- *Alternatives*: Regenerate the scan from a runtime build whose Send to Helix task logs retain the Helix job identifiers.

> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.

**Last agent output:**
```
│ logs for runtime build 1567845 contained no `Sent Helix Job: ` evidence, so Helix work
│ items and xharness console failures cannot be identified.","context":"Validated platform
│ submission logs 723, 652, 535, 619, 698, 589, and 504 for the selected failed
│ build.","alternatives":"Regenerate the scan from a runtime build whose Send to Helix task logs…
└ 16 lines…
Runtime scan is incomplete: the selected build’s required Helix submission logs lacked Helix job identifiers, preventing work-item and xharness-console analysis. Reported the missing data for regeneration from a build retaining those logs.
Changes +0 -0
Duration 1m 27s
Tokens ↑ 588.0k (544.7k cached, 43.3k written) • ↓ 5.2k (1.1k reasoning)
Resume copilot --resume=01f5a407-cac0-47c1-9634-597600005d4b
```

### Action Required

**Assign this issue to an agent** to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/dotnet/xharness/actions/runs/33031694972
````

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.

- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow runtime-failure-observer.agent failure in https://github.com/dotnet/xharness/actions/runs/33031694972`

> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>

> Generated from [Runtime Failure Observer (xharness)](https://github.com/dotnet/xharness/actions/runs/33031694972) · 25.8 AIC · [◷](https://github.com/search?q=repo%3Adotnet%2Fxharness+is%3Aissue+%22gh-aw-workflow-id%3A+runtime-failure-observer.agent%22&type=issues)
> - [x] expires on Sep 3, 2026, 2:02 AM UTC

Start with .github/workflows/runtime-failure-observer.agent.md and the failed run 33031694972, then load .github/skills/agentic-workflows/SKILL.md. Inspect the runtime build 1567845 submission logs and determine why the required “Sent Helix Job: ” evidence is unavailable; done means the workflow can identify Helix work items and xharness console failures or clearly regenerate from a suitable build.

Written by the indexing model from the issue text.