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

[github-actions]

🏥 CI Failure Investigation - Run #34277

Summary

CI run 34277 triggered by the "Use runtime-import macros for frontmatter imports" change now fails early: the lint-go job reports unformatted Go files, and Integration: Parser Location & Validation hits TestAgentImportWithToolsArray because the test still expects agent markdown in ImportsResult.MergedMarkdown even though runtime imports move the content into ImportPaths.

Failure Details

• Run: 34277
• Commit: 6278b7d
• Trigger: push

Root Cause Analysis

The lint-go job executes go fmt ./..., prints the message "❌ Code is not formatted. Run 'make fmt' to fix." and exits with status 1. The PR introduced Go files that have not been gofmt'd yet.
The integration test failure in pkg/parser/agent_import_integration_test.go:102 occurs because the updated runtime-import macro implementation treats imports without inputs as runtime imports and records them in ImportsResult.ImportPaths instead of inlining their markdown. The test still asserts that MergedMarkdown is non-empty, which no longer holds for imports without inputs.

Failed Jobs and Errors

• lint-go: go fmt ./... stopped with exit code 1 after emitting the unformatted-files message.
• Integration: Parser Location & Validation: TestAgentImportWithToolsArray fails with agent_import_integration_test.go:102: Expected MergedMarkdown to contain agent markdown content.

Investigation Findings

• Running go fmt ./... (or make fmt) on this branch should expose the specific files that need formatting; applying the formatter should resolve the lint failure.
• ProcessImportsFromFrontmatterWithManifest now captures imports without inputs in ImportPaths for runtime-import macros, so custom agents imported without inputs no longer contribute to MergedMarkdown.

Recommended Actions

• Run make fmt, commit the formatted Go files, and rerun lint-go so go fmt no longer reports unformatted files.
• Update TestAgentImportWithToolsArray so it asserts that the agent import appears in ImportsResult.ImportPaths (and that MergedMarkdown can stay empty when no inputs are provided) so the test covers the new runtime-import behavior.

Prevention Strategies

• Run make fmt locally before pushing Go changes so lint-go never sees unformatted files.
• When a change introduces runtime-import macros, also update parser integration tests to match the new ImportPaths/MergedMarkdown contract.

AI Team Self-Improvement

• Reminder for future investigations: when runtime-import handling changes, double-check parser tests that inspect MergedMarkdown and update them to look at ImportPaths so they stay aligned with the new compile/runtime split.

Historical Context

• These failures appeared with the runtime-import macro change in this run; the same tests and lint step were green before the change, so the new behavior is triggering the regressions.

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 8, 2026, 5:06 PM UTC

[github-actions]

Run #34289 (https://github.com/github/gh-aw/actions/runs/21784016602) still fails in Integration: Parser Location & Validation because TestAgentImportWithToolsArray keeps expecting ImportsResult.MergedMarkdown to contain the custom agent markdown even when the import has no inputs. The new runtime-import macros populate ImportsResult.ImportPaths for those imports, so MergedMarkdown now stays empty and the assertion fails at agent_import_integration_test.go:102. lint-go was cancelled after this failure. No new issue was created because this run is a duplicate of #14392, which was opened minutes ago for the same regression.

AI generated by CI Failure Doctor

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster

[github-actions]

Run 34292 still fails in Integration: Parser Location & Validation for the same reason: TestAgentImportWithToolsArray now sees an empty ImportsResult.MergedMarkdown because runtime import macros record imports without inputs via ImportPaths, so the custom agent markdown is no longer inlined. No other jobs failed. The failure message is the same:

agent_import_integration_test.go:102: Expected MergedMarkdown to contain agent markdown content

Since this is the same root cause described above, no new issue is needed right now.

AI generated by CI Failure Doctor