[CI Failure Doctor] CI Failure Investigation - plugin validation rejects Claude workflow

[github-actions]

🏥 CI Failure Investigation - Run #34446

Summary

TestCompileWorkflowWithPluginImportsClaudeEngine now fails because the compiler rejects plugin usage for Claude even though Claude and Codex installation steps include plugin installation.

Failure Details

• Run: 21803361884
• Commit: 8fed717
• Trigger: push

Root Cause Analysis

validatePluginSupport() guards plugin installation by calling agenticEngine.SupportsPlugins(). Claude and Codex never set BaseEngine.supportsPlugins to true, so the compiler throws engine 'claude' does not support plugins... before it can emit any installation steps. The regression surfaces as the failing unit test that expects the compiler to succeed when plugins are declared alongside Claude.

Failed Jobs and Errors

• test job failed with the message:

  engine 'claude' does not support plugins. The following plugins cannot be installed: anthropic/plugin-one
  Only the 'copilot' engine currently supports plugin installation.
  

Investigation Findings

• Claude and Codex intended to support plugins (plugin installation steps are generated in GetInstallationSteps), but the engines were never marked as supporting plugins, so the validation in validatePluginSupport rejects their workflows.
• validatePluginSupport hard-codes the supported engine list in the error message, so it now misinforms users even if additional engines support plugins.
• Attempted to run go test ./pkg/workflow -run TestCompileWorkflowWithPluginImports with Go 1.25.6, but the module downloads (e.g., github.com/cli/go-gh/v2@v2.13.0) were blocked (Forbidden from proxy.golang.org), so the test suite could not be executed locally.

Recommended Actions

• Set supportsPlugins: true for Claude and Codex and update the validation message to list every engine that advertises plugin support so the compiler approvingly allows their plugin workflows.

Prevention Strategies

• Keep the BaseEngine.supportsPlugins flag in sync with any engine that emits plugin installation steps and add regression tests that cover the validation path when plugin info is present.

AI Team Self-Improvement

When touching plugin installation logic, always verify that the engines you surface plugin steps for advertise SupportsPlugins() so the validation layer and user-facing error messages stay aligned.

Historical Context

No prior CI Failure Doctor investigations were found for this specific plugin validation mismatch in the recent run history.

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:53 PM UTC