Phase 5: Remaining gh-aw workflows (Docs Health, Dependency Advisory, Standards Sync, ContentTwin Audit) #236

Context

Part of the GitHub Agentic Workflows rollout — Discussion #228.

Depends on: #235 (Phase 4 — cross-org deployment must be complete first)

Goal

Implement the lower-priority workflows from the backlog. Each follows the same TDD cycle as Phases 1–3: scenario spec → workflow markdown → compile → staged → live.

Workflow backlog

P2 — Documentation Health (docs-health-check.md)

• Trigger: schedule, weekly
• Purpose: audit docs freshness across repos; open an issue listing files not updated in 90+ days
• Scenario spec: tests/aw/docs-health-check/scenarios.md

P2 — Dependency Advisory (dependency-advisory.md)

• Trigger: pull_request touching package.json, go.mod, requirements.txt, or similar dep files
• Purpose: AI-powered risk assessment of dep changes beyond what Dependabot provides — flag major version bumps, known-vulnerable packages, unusual new transitive deps
• Scenario spec: tests/aw/dependency-advisory/scenarios.md

P3 — Cross-repo Standards Sync (standards-sync.md)

• Trigger: schedule, monthly (first Monday)
• Purpose: check all repos against org standards (AGENTS.md, CODEOWNERS, required workflow files); open PRs to repos that are out of sync
• Scenario spec: tests/aw/standards-sync/scenarios.md

P3 — ContentTwin Content Audit (content-twin-audit.md)

• Trigger: schedule, daily
• Purpose: review ContentTwin's content pipeline health; open an issue if content is stale, queue is empty, or publishing errors detected
• Repo scope: ContentTwin only
• Scenario spec: tests/aw/content-twin-audit/scenarios.md

Process

Implement these in priority order (P2 before P3). Each workflow must go through the full TDD cycle independently — do not batch them into a single PR.

Acceptance Criteria (per workflow)

• Scenario spec written and reviewed before workflow markdown
• Compiles cleanly in CI
• Staged run matches spec
• Live verified
• Documented in docs/aw/
• All changes via PR