Can\\u0026#39;t find \\u0026#39;action.yml\\u0026#39;, \\u0026#39;action.yaml\\u0026#39; or \\u0026#39;Dockerfile\\u0026#39; under \\n\\u0026#39;/home/runner/work/gh-aw/gh-aw/actions/setup\\u0026#39;. Did you forget to run \\nactions/checkout before running your local action?\\n```\\n\\n**Important:** The actual memory push succeeds — data is correctly written to `memory/pr-triage` branch. The failure only affects the post-job cleanup phase.\\n\\n### Evidence\\n\\nFrom run [#289](https://github.com/github/gh-aw/actions/runs/23580548645) logs (`push_repo_memory` job):\\n- ✅ Checked out branch `memory/pr-triage`\\n- ✅ Committed and pushed 3 files (`pr-triage-latest.json`, `pr-triage-summary.md`, `README.md`)\\n- ❌ Post-job cleanup fails: can\\u0026#39;t find `actions/setup`\\n\\n### Impact\\n\\n- PR Triage Agent reports are still being generated (the `agent` job succeeds)\\n- Repo memory is being saved successfully\\n- But the overall workflow run is marked as `failure` due to the cleanup error\\n\\n### Suggested Fix\\n\\nOptions:\\n1. **Add a checkout step** at the end of `push_repo_memory` to restore the workspace to the main branch before cleanup\\n2. **Use `persist-credentials: false` + sparse checkout on main** as the last step to restore `actions/setup`\\n3. **Set `continue-on-error: true`** on steps that might leave the workspace on the memory branch\\n\\nThe fix should be implemented in the workflow compiler\\u0026#39;s `push_repo_memory` job generation, so all workflows that use repo-memory benefit from the fix.\\n\\n### Priority\\n\\n**P1** — New regression, 2 consecutive failures starting 2026-03-26T00:12\\n\\n\\u0026gt; Detected by [§23593331592](https://github.com/github/gh-aw/actions/runs/23593331592) — Workflow Health Manager\\n\\n\\n\\n\\n\\u0026gt; [!NOTE]\\n\\u0026gt; \\n\\u0026gt; \\u003cb\\u003e🔒 Integrity filter blocked 3 items\\u003c/b\\u003e\\n\\u0026gt;\\n\\u0026gt; The following items were blocked because they don\\u0026#39;t meet the GitHub integrity level.\\n\\u0026gt;\\n\\u0026gt; - [#21703](https://github.com/github/gh-aw/issues/21703) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below \\u0026#34;approved\\u0026#34;.\\n\\u0026gt; - [#18407](https://github.com/github/gh-aw/issues/18407) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below \\u0026#34;approved\\u0026#34;.\\n\\u0026gt; - [#21784](https://github.com/github/gh-aw/issues/21784) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below \\u0026#34;approved\\u0026#34;.\\n\\u0026gt;\\n\\u0026gt; To allow these resources, lower `min-integrity` in your GitHub frontmatter:\\n\\u0026gt;\\n\\u0026gt; ```yaml\\n\\u0026gt; tools:\\n\\u0026gt; github:\\n\\u0026gt; min-integrity: approved # merged | approved | unapproved | none\\n\\u0026gt; ```\\n\\u0026gt;\\n\\u0026gt; \\n\\n\\n\\u0026gt; Generated by [Workflow Health Manager - Meta-Orchestrator](https://github.com/github/gh-aw/actions/runs/23593331592) · [◷](https://github.com/search?q=repo%3Agithub%2Fgh-aw+is%3Aissue+%22gh-aw-workflow-call-id%3A+github%2Fgh-aw%2Fworkflow-health-manager%22\\u0026amp;type=issues)\\n\\u0026gt; - [x] expires on Mar 27, 2026, 12:14 PM UTC\\n\\n\\n\\n\\n\",\"state\":\"OPEN\",\"user\":{\"login\":\"github-actions\"},\"labels\":[\"agentic-workflows\",\"cookie\"],\"comments\":2,\"created_at\":\"2026-03-26T12:14:05Z\",\"updated_at\":\"2026-03-26T12:35:26Z\"},{\"number\":23108,\"title\":\"Duplicate tool-usage aggregation logic in audit report pipeline\",\"body\":\"### Overview\\nRecent commit `[REDACTED]` adds/updates agentic analysis paths and now contains a duplicated tool-usage aggregation block in two CLI code paths.\\n\\nThe duplicated block is large enough to be maintenance-significant and already diverges slightly (one path sorts results, the other does not), which increases risk of behavior drift.\\n\\n### Critical Information\\n- Pattern type: exact/near-exact duplication\\n- Severity