Diagnose AWF Failures

Single entry point for diagnosing AWF failures. The canonical knowledge lives in the diagnosis registry — this skill only routes and reports.

Procedure

1. Read the index — docs/diagnostics/README.md for boundary routing and specialist references, and docs/diagnostics/agent-playbook.md for the report shape and safety rules.
2. Fingerprint the run: AWF version, runner type (GitHub-hosted / self-hosted / ARC+DinD / GHES / GHEC), DOCKER_HOST, GITHUB_SERVER_URL, container runtime, provider, auth mode. Use unknown where unverified.
3. Classify the failing boundary: runner, runtime, network, auth, ci, security.
4. Load only matching records: