[CI Failure Doctor] Timeout_minutes trigger integration misc failure

[github-actions]

🏥 CI Failure Investigation - Run #34788

Summary

The Integration: Workflow Misc Part 2 job now fails because pkg/workflow/max_turns_test.go still compiles a workflow that uses the removed timeout_minutes field, so the workflow compiler rejects it before the test assertions ever run.

Failure Details

• Run: 21892828866
• Commit: 634feae
• Trigger: push

Root Cause Analysis

The schema no longer allows timeout_minutes, so the fixture under test (lines 8‑11 of max_turns_test.go) triggers a compilation error (Unknown property: timeout_minutes) when the compiler parses the workflow frontmatter. The test never gets to the assertions that would verify max-turns behavior.

Failed Jobs and Errors

• Integration: Workflow Misc Part 2 — pkg/workflow/max_turns_test.go fails because the workflow file contains timeout_minutes: 15, which the compiler rejects with error: Unknown property: timeout_minutes. Did you mean 'timeout-minutes'?.

Investigation Findings

• The only failing job is the integration suite for workflow misc components, and its log points directly to the fixture in max_turns_test.go.
• The frontmatter in that test was not updated after the schema migration that removed timeout_minutes in favor of timeout-minutes.
• Local reproduction attempts were blocked: go test ./pkg/workflow -run TestMaxTurnsCompilation tried to download Go 1.25.0 and received Forbidden, and forcing GOTOOLCHAIN=local hit go.mod requires go >= 1.25.0 (running go 1.24.12).

Recommended Actions

• Update pkg/workflow/max_turns_test.go and any other fixtures that try to set timeout_minutes so they use timeout-minutes (and rerun math-turns coverage just to be safe).
• Re-run the Integration: Workflow Misc Part 2 job once the fixture is updated.
• Ensure the runners (or dev laptops) can access Go 1.25.0 (allow proxy downloads or pre-install the toolchain) so tests can be re-run locally without hitting go.mod requirements.

Prevention Strategies

• Consider adding a lint or test that fails early when new fixtures use deprecated frontmatter keys such as timeout_minutes.
• Keep documentation (e.g., docs/guides/upgrading.md and frontmatter reference pages) and codemods synchronized with schema removals, and search for the old key when changing schemas.

AI Team Self-Improvement

• When a frontmatter property is removed, update every fixture/test that uses it before rerunning the workflows and codemods that touch that property.
• Include Go toolchain availability notes in your checklist so local go test runs report actionable errors instead of getting blocked by go1.25.0 downloads.

Historical Context

• The timeout_minutes field was previously removed from the schema and documented in docs/src/content/docs/guides/upgrading.md and the frontmatter reference guide, so this is a regression for the integration watchdog.

AI generated by CI Failure Doctor

To add this workflow in your repository, run gh aw add githubnext/agentics/workflows/ci-doctor.md@ea350161ad5dcc9624cf510f134c6a9e39a6f94d. See usage guide.

• expires on Feb 12, 2026, 4:41 AM UTC