Phase 0: Install and initialize gh-aw in .github-private #230

Context

Part of the GitHub Agentic Workflows rollout planned in Discussion #228.

Phase 0 establishes the foundation before any individual workflows are authored.

Tasks

1. Install gh-aw extension support in CI

Add a step to .github/workflows/lint.yml that installs the gh-aw extension and runs gh aw compile. The step should:

• Install via curl -sL https://raw.githubusercontent.com/github/gh-aw/main/install-gh-aw.sh | bash
• Run gh aw compile to validate all *.md workflow files
• Fail the CI job if compilation fails
• Only run if .github/workflows/*.md files exist (skip gracefully if none yet)

2. Initialize gh-aw in this repo

Run gh aw init to generate:

• .github/agents/agentic-workflows.agent.md — the dispatcher agent config
• Any MCP server integration config

Configure the engine to use Claude (CLAUDE_CODE_OAUTH_TOKEN is already in repo secrets).

3. Write the test convention doc

Create tests/aw/README.md documenting how gh-aw workflows are tested in this repo:

• Scenario spec format (written before workflow markdown)
• How to run staged smoke tests (gh aw run <name> --staged)
• Compile validation as the CI gate
• Definition of Done checklist

4. Create the tests/aw/ directory structure

Create the directory with the README and placeholder subdirectories for the first two planned workflows:

• tests/aw/issue-triage/ (empty, with .gitkeep)
• tests/aw/ci-failure-analyst/ (empty, with .gitkeep)

Acceptance Criteria

• gh aw compile runs in CI and passes (with zero workflows — baseline)
• .github/agents/agentic-workflows.agent.md exists and references Claude as engine
• tests/aw/README.md exists and covers the 3-level test methodology
• All changes land via a PR (not direct push to main)