[CI Failure Doctor] 🎯 Claude plugin validation blocks workflow compilation

[github-actions]

🏥 CI Failure Investigation - Run #34447

Summary

The test job now fails because the workflow compiler rejects engine: claude workloads that import plugins even though the compiler emits Claude-specific plugin installation steps.

Failure Details

• Run: 21803388464
• Commit: 5350642
• Trigger: push

Root Cause Analysis

validatePluginSupport (pkg/workflow/engine_validation.go) reads agenticEngine.SupportsPlugins() to decide whether plugin imports are allowed. ClaudeEngine (pkg/workflow/claude_engine.go) never sets supportsPlugins: true, so validation still believes only Copilot supports plugins and raises:

engine 'claude' does not support plugins. The following plugins cannot be installed: anthropic/plugin-one

Only the 'copilot' engine currently supports plugin installation.

Even though Claude installation steps call GeneratePluginInstallationSteps, the capability flag stays false, so TestCompileWorkflowWithPluginImportsClaudeEngine fails before compilation completes.

Failed Jobs and Errors

• test – TestCompileWorkflowWithPluginImportsClaudeEngine fails at pkg/workflow/plugin_import_test.go:296 with the error above.

Investigation Findings

• Running go test -run TestCompileWorkflowWithPluginImportsClaudeEngine ./pkg/workflow reproduces the failure.
• The workflow harness writes a shared plugins file (shared-plugins.md), imports it, and expects claude plugin install anthropic/plugin-one to appear in the lock file but validation aborts earlier.
• The log explicitly reports that only Copilot supports plugins, so the test never reaches the plugin-installation assertions.

Recommended Actions

• Set supportsPlugins: true for the Claude engine (and align Codex if it’s supposed to support plugins as well) so validatePluginSupport permits plugin imports.
• Update the error message in validatePluginSupport to list the engines that actually support plugins instead of hard-coding Copilot.

Prevention Strategies

Keep capability flags (e.g., supportsPlugins) in sync with compilation features; derive the supported-engine list from the registry rather than hard-coding a single name.

AI Team Self-Improvement

When adding plugin steps for a new engine, also update the corresponding capability flag and ensure validation messages/tests are aligned.

Historical Context

Unable to search existing "[CI Failure Doctor]" issues or cookies-labeled reports because the CLI has no authenticated GitHub access in this environment.

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 9, 2026, 6:59 PM UTC

[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