Summary

Add a new section to the waza docs site (site/src/content/docs/guides/) covering how to use waza in CI/CD pipelines across GitHub Actions and Azure DevOps.

Motivation

Waza users need clear guidance on integrating evals and token checks into their CI workflows. Currently there's no docs page showing how to install waza, run evals, and gate PRs in automated pipelines. This is a common first question from teams adopting waza.

Proposed Content

Guide: ci-integration.mdx

1. Installing waza in CI

• Via azd extension (recommended): azd ext install microsoft.azd.waza
• Via binary download (alternative)

2. GitHub Actions

• Running evals on PR (azd waza run)
• Token budget checks (waza tokens check / waza tokens diff)
• Uploading results as artifacts
• Pass/fail gating with thresholds
• Example workflow file

3. Azure DevOps Pipelines

• Same capabilities adapted for ADO YAML syntax
• Pipeline task examples
• Artifact publishing

4. GitLab CI (brief)

• Minimal example showing portability

5. Best Practices

• When to run evals (on skill changes only vs. every PR)
• Path filters to avoid unnecessary runs
• Caching waza installation
• Handling eval failures (informational vs. blocking)

Reference

The GitHub Copilot for Azure team already has a working GitHub Actions integration:

`yaml

Their pattern (from .github/workflows/eval.yml)

• uses: Azure/setup-azd@v2
• run: |
  azd config set alpha.extensions on
  azd ext source add -n waza -t url -l https://raw.githubusercontent.com/microsoft/waza/main/registry.json
  azd ext install microsoft.azd.waza
• run: azd waza run evals/eval.yaml --output-dir ./results
  `

This should be generalized and documented for all waza users.

Acceptance Criteria

• New guide page at site/src/content/docs/guides/ci-integration.mdx
• GitHub Actions example workflow (copy-pasteable)
• Azure DevOps pipeline example
• Token budget diff integration example (references feat: Token budget diff CLI command + optional GitHub Action wrapper #81)
• Added to site navigation sidebar
• Builds successfully: cd site && npm run build

Labels

enhancement, docs, priority:p1