[CI Failure Doctor] CI Failure Investigation - Run #37649

[github-actions]

Summary

make recompile aborts because the newly added smoke-copilot.md workflow does not pass the schema checks: the compiler emits Invalid workflow YAML written to: .github/workflows/smoke-copilot.invalid.yml and exits with ✗ compilation failed after compiling 157/158 workflows.

Failure Details

• Run: 22337933863
• Commit: e0f45bc
• Trigger: push

Root Cause Analysis

The compiler succeeds for every other workflow but stops when it reaches smoke-copilot.md. It writes a .invalid.yml file to the workspace, prints the warning, and shuts down with compilation failed. The log does not include the specific schema violation, so the next debugging step is to run gh aw compile .github/workflows/smoke-copilot.md (or make recompile) and inspect the emitted .invalid.yml to determine what field is being rejected (safe-outputs/jobs/messages, etc.). Local reproduction in this environment was blocked because the Go command cannot download the go1.25 toolchain from proxy.golang.org.

Failed Jobs and Errors

• build – make recompile – Invalid workflow YAML written to: .github/workflows/smoke-copilot.invalid.yml → ✗ compilation failed (failure occurs after all other workflows compile successfully, so the new workflow is the root cause)

Investigation Findings

• Running make recompile compiles 158 workflows; the only failure occurs on the very last one, smoke-copilot.md, which triggers the .invalid.yml warning.
• The emitted warning is the only sign of failure in the logs, so the precise schema rejection is currently unknown without reproducing the compilation locally and opening the invalid YAML.
• I attempted to reproduce via gh aw compile .github/workflows/smoke-copilot.md, but go refuses to fetch the go1.25 toolchain in this sandbox (proxy.golang.org returns Forbidden), so I couldn't recreate the .invalid output here.

Recommended Actions

• Run gh aw compile .github/workflows/smoke-copilot.md (or make recompile) in an environment with a working go1.25 toolchain, then open the generated .github/workflows/smoke-copilot.invalid.yml to pinpoint the schema violation and adjust the frontmatter accordingly.
• Once the violating field is fixed, re-run make recompile to ensure the workflow no longer triggers an .invalid.yml warning and that the new .lock.yml is updated.
• If the workflow relies on new safe-output constructs, double-check that the compiler supports those constructs or extend the compiler so the workflow can be validated.

Prevention Strategies

• Require people to run make recompile (or gh aw compile (workflow).md) before landing new workflows so invalid frontmatter cannot reach CI.
• Capture the .invalid.yml output immediately (the compiler writes it next to the .lock file) so reviewers know exactly which schema rule was violated.

AI Team Self-Improvement

Before landing a new workflow, run make recompile, inspect any emitted .invalid.yml, and fix the frontmatter or compiler support before pushing.

Historical Context

This is the first occurrence of this failure pattern; it started as soon as the smoke-copilot workflow was introduced in the latest push.

🩺 Diagnosis provided by CI Failure Doctor

To install this workflow, run gh aw add githubnext/agentics/workflows/ci-doctor.md@ea350161ad5dcc9624cf510f134c6a9e39a6f94d. View source at https://github.com/githubnext/agentics/tree/ea350161ad5dcc9624cf510f134c6a9e39a6f94d/workflows/ci-doctor.md.

• expires on Feb 25, 2026, 5:48 AM UTC