[CI Failure Doctor] Golden workflows expect old MCP server version

[github-actions]

🏥 CI Failure Investigation - Run #36941

Summary

New workflow compilations now pull ghcr.io/github/github-mcp-server:v0.31.0, but the wasm golden fixtures/tests were hard-coded to v0.30.3, so build-wasm/test jobs fail before any other logic can run.

Failure Details

• Run: 22223796319
• Commit: 293acf9
• Trigger: push

Root Cause Analysis

The wasm golden test suite emits actions jobs that call download_docker_images.sh and Start MCP Gateway with the current MCP server container (v0.31.0), but the .golden files and string assertions were still comparing against ghcr.io/github/github-mcp-server:v0.30.3. Every fixture therefore surfaces a diff for the container field and fails immediately.

Failed Jobs and Errors

• build-wasm – TestWasmGolden_CompileFixtures/with-safe-outputs stopped because the generated workflow now references 3 container image downloads and Start MCP Gateway with v0.31.0 while the golden lock still had v0.30.3.
• test – TestWasmGolden_CompileFixtures/* repeatedly reported output differs from golden for every fixture, with the diff showing the container image bump from v0.30.3 to v0.31.0 in the compiled activation jobs.

Investigation Findings

• Every golden fixture under pkg/workflow/testdata/wasm_golden/TestWasmGolden_CompileFixtures had the old MCP server image version in both the download_docker_images.sh command and the container field, so the generated lock file mismatched the new compiler output.
• Go tests such as mcp_config_test, docker_predownload_test, copilot_engine_test, codex_engine_test, github_remote_mode_test, and copilot_github_mcp_test also asserted on the old v0.30.3 string.
• scratchpad/layout.md still documented the previous default version.

Recommended Actions

• Update every golden fixture and test string that referenced ghcr.io/github/github-mcp-server:v0.30.3 so they expect v0.31.0.
• Introduce a helper (or use constants.DefaultGitHubMCPServerVersion) in tests/fixtures so future MCP server bumps don’t require editing dozens of strings manually.

Prevention Strategies

Document the MCP server toolchain bump process and regenerate the wasm golden fixtures whenever DefaultGitHubMCPServerVersion changes so the compiled outputs stay synchronized with the tests.

AI Team Self-Improvement

When an MCP server release happens, also refresh every wasm golden fixture, golden lock, and string assertion that mentions ghcr.io/github/github-mcp-server and make sure the documentation (e.g., in scratchpad/layout.md) reflects the new default version.

Historical Context

Our golden suite has failed immediately after past MCP server releases because the fixtures were pinned to the previous image tag; the same pattern shows up any time the default ghcr.io/github/github-mcp-server tag is bumped without updating the expectations.

🩺 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 21, 2026, 12:29 PM UTC