[aw] Documentation Freshness Check failed

[github-actions]

Workflow Failure

Workflow: Documentation Freshness Check
Branch: main
Run: https://github.com/githubnext/ado-aw/actions/runs/28017171283

Warning

Engine Failure: The copilot engine terminated unexpectedly.

Last agent output:

  │ git branch --show-current
  └ 2 lines...
● create_pull_request (MCP: safeoutputs) · title: "docs: fix documentation drift — schedule frequen…
  └ {"result":"success","patch":{"path":"/tmp/gh-aw/aw-docs-fix-schedule-fre...
PR created. The audit found one meaningful inconsistency:
**`prompts/create-ado-agentic-workflow.md`** — the Step 3 schedule frequency table was missing `weekly` (plain, without `on <day>`). This option is:
- Fully supported by `src/fuzzy_schedule.rs` (`parse_weekly_schedule` returns `FuzzySchedule::Weekly { day: None }` when no day is specified)
- Documented in `docs/schedule-syntax.md`
- But absent from the agent authoring guide, meaning agents wouldn't know to use it
Everything else checked out accurately: CLI commands, front matter fields, safe output tools, network allowlist, engine defaults, MCP config, and AGENTS.md architecture tree all matched the codebase.

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/28017171283

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 https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md
• Type debug the agentic workflow doc-freshness-check failure in https://github.com/githubnext/ado-aw/actions/runs/28017171283

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:

safe-outputs:
  report-failure-as-issue: false

Generated from Documentation Freshness Check · 1.9K AIC · ◷

• expires on Jun 30, 2026, 10:06 AM UTC