githubnext / githubnext/ado-aw
[aw] Agent Documentation Maintainer failed
- Dominant language
- Rust
- Stars
- 23
- Forks
- 8
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 22
Description
### Workflow Failure
**Workflow:** [Agent Documentation Maintainer](https://github.com/githubnext/ado-aw/blob/main/.github/workflows/doc-freshness-check.md)
**Branch:** main
**Run:** https://github.com/githubnext/ado-aw/actions/runs/34562717291
> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.
**Last agent output:**
```
└ 11 lines…
● List open PRs for githubnext/ado-aw (shell) 20s
│ cd /home/runner/work/ado-aw/ado-aw && github list_pull_requests --owner githubnext --repo ado-aw
│ --state open --fields '["number","title","html_url"]' 2>&1 | head -60
└ 15 lines…
Multiple open PRs already target the exact same gap: `container_runtime.rs` missing from AGENTS.md's architecture tree. Let me verify this is indeed a real gap and check if there's anything else to find, since that one is already covered extensively.
● Check container_runtime.rs existence and AGENTS.md mention (shell)
│ cd /home/runner/work/ado-aw/ado-aw && find src -iname "container_runtime*"
│ grep -n "container_runtime\|container_invocation" AGENTS.md
└ 3 lines…
```
### 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/ado-aw/actions/runs/34562717291
````
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 doc-freshness-check failure in https://github.com/githubnext/ado-aw/actions/runs/34562717291`
> [!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 [Agent Documentation Maintainer](https://github.com/githubnext/ado-aw/actions/runs/34562717291) · 73.2 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fado-aw+is%3Aissue+%22gh-aw-workflow-id%3A+doc-freshness-check%22&type=issues)
> - [x] expires on Sep 18, 2026, 4:57 AM UTC
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with .github/workflows/doc-freshness-check.md and the linked failed run, then inspect AGENTS.md alongside src/container_runtime.rs as indicated by the agent output. Confirm why the documentation-maintainer agent terminated and whether the existing PRs already address the reported architecture-tree gap. Done means the failure is resolved without duplicating work already underway.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100