[aw] SelfCare / Dashboard Performance has cache-memory miss misconfiguration

### Workflow Failure

**Workflow:** [SelfCare / Dashboard Performance](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/self-care-dashboard-performance.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/34522695098

> [!WARNING]
> **Code Push Failed**: A code push safe output failed, and subsequent safe outputs were cancelled.

**Code Push Errors:**
- `create_pull_request`: Cannot create pull request: patch modifies files outside the allowed-files list. Add the files to the allowed-files configuration field or remove them from the patch.

Show 2 blocked files

`dashboard/site/test/unit/presenter.test.js`, `dashboard/site/test/unit/ui-elements.test.js`

> [!WARNING]
>
> Cache Configuration Problem: cache miss detected after cache restore succeeded.
>
> The agent reported a cache miss (`missing_data` with `reason: cache_memory_miss`) after the workflow successfully restored cache-memory for this run. This likely indicates the prompt is misconfigured and the agent cannot locate the correct file path within the cache directory.
>
> This warning is shown only when a cache restore matched an existing key. Cache misses can be expected on first runs and on branches where `actions/cache` has no visible entries due to branch scoping.
>
> Review the [cache-memory configuration](https://github.github.com/gh-aw/reference/cache-memory/) and ensure the agent prompt correctly references files inside the cache directory.
>
> **File naming convention:** Cache files are stored at `/tmp/gh-aw/cache-memory/` (default) or `/tmp/gh-aw/cache-memory-{id}/` for additional caches. Use descriptive file and directory names with subdirectories for organization.
>
>

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

**Missing Tools:**
- **upload\_artifact**: The workflow requires uploading self-care-dashboard-performance-34522695098, but upload\_artifact is not available in the allowed safe-output tools for this run.

Alternatives:

| Tool | Alternative |
| --- | --- |
| upload\_artifact | Evidence is available locally at /home/runner/work/gh-aw-cao/gh-aw-cao/self-care-dashboard-performance-evidence and summarized in the pull request body. |

### 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/githubnext/gh-aw-cao/actions/runs/34522695098
````

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 self-care-dashboard-performance failure in https://github.com/githubnext/gh-aw-cao/actions/runs/34522695098`

> [!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 [SelfCare / Dashboard Performance](https://github.com/githubnext/gh-aw-cao/actions/runs/34522695098) · copilot · 286.1 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+self-care-dashboard-performance%22&type=issues)
> - [x] expires on Sep 17, 2026, 8:17 PM UTC

Start with .github/workflows/self-care-dashboard-performance.md and compare its cache-memory configuration with the cache-memory reference linked in the issue. Review the allowed-files configuration against dashboard/site/test/unit/presenter.test.js and dashboard/site/test/unit/ui-elements.test.js, and check the safe-output tools for upload_artifact. Done means the workflow can locate its cache data, permit only intended files, provide the required artifact tool, and complete successfully on a rerun.

Written by the indexing model from the issue text.