[aw] Daily Memory Leak Hunter is missing required data

### Workflow Failure

**Workflow:** [Daily Memory Leak Hunter](https://github.com/dotnet/maui/blob/main/.github/workflows/daily-leak-hunter.md)
**Branch:** main
**Run:** https://github.com/dotnet/maui/actions/runs/34916389987

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

**Missing Data:**
- **Open \[leak-scan\] issue titles and bodies for canonical rooting-API de-duplication**: The read-only GitHub MCP response was removed by the runner integrity filter. Exact semantic searches also returned filtered records rather than inspectable titles, so I cannot determine whether the six empirically confirmed rooting APIs already have open
\[Content truncated due to length\]
- *Context*: All six standalone Microsoft.Maui.Controls 10.0.0 net10.0 probes passed with Control=0, Mitigation=0, Leaky=30: TransformGroup.Children, PathGeometry.Figures, PathFigure.Segments, GradientBrush.GradientStops, VisualElement.Resources, and ResourceDictionary
\[Content truncated due to length\]
- *Alternatives*: Provide an inspectable list of open issues labeled agentic-workflows whose titles begin with \[leak-scan\], or precompute already-filed-apis.txt before the integrity-filtered agent step.

### 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/maui/actions/runs/34916389987
````

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 daily-leak-hunter failure in https://github.com/dotnet/maui/actions/runs/34916389987`

> [!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 [Daily Memory Leak Hunter](https://github.com/dotnet/maui/actions/runs/34916389987) · 198.1 AIC · [◷](https://github.com/search?q=repo%3Adotnet%2Fmaui+is%3Aissue+%22gh-aw-workflow-id%3A+daily-leak-hunter%22&type=issues)
> - [x] expires on Sep 22, 2026, 1:23 AM UTC

Start with the Daily Memory Leak Hunter workflow at .github/workflows/daily-leak-hunter.md and inspect the failed run linked in the issue. The report says the read-only GitHub MCP response was removed by the runner integrity filter, blocking inspection of open [leak-scan] issues. Determine how that workflow can access an inspectable list of existing issue titles and bodies; done when the workflow can de-duplicate the six confirmed rooting APIs without filtered records.

Written by the indexing model from the issue text.