Add MCP gateway log rendering to step summary

[Copilot]

MCP gateway logs were not visible in the workflow step summary, requiring manual artifact inspection to debug gateway startup issues.

Changes

JavaScript Parser (actions/setup/js/parse_mcp_gateway_log.cjs)

• Reads gateway stderr from /tmp/gh-aw/mcp-logs/gateway/stderr.log
• Wraps content in collapsible <details> with code fence
• Handles empty logs and whitespace normalization

Go Code Generation

• Added generateMCPGatewayLogParsing() in compiler_yaml_ai_execution.go
• Integrated into workflow compilation after safe-inputs log parsing
• Step executes with if: always() to capture logs on failure

Generated Step

- name: Parse MCP gateway logs for step summary
  if: always()
  uses: actions/github-script@v8.0.0
  with:
    script: |
      const { setupGlobals } = require('/opt/gh-aw/actions/setup_globals.cjs');
      setupGlobals(core, github, context, exec, io);
      const { main } = require('/opt/gh-aw/actions/parse_mcp_gateway_log.cjs');
      await main();

The step is automatically included in all workflows using MCP tools.

Original prompt

Add a step that renders the MCP gateway log into the step summary.

Render using a details section and a code section in markdown. Use JavaScript script stored in actions/setup

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[github-actions]

🎉 Yo ho ho! Changeset Generator found the treasure and completed successfully! ⚓💰

[github-actions]

✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟

[github-actions]

📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤

[github-actions]

💫 TO BE CONTINUED... Smoke Claude failed! Our hero faces unexpected challenges...