Add workflow health checks, MCP config, and startup diagnostics

[Copilot]

GitHub Actions workflows were failing silently or with unclear errors due to missing environment validation and poor error visibility.

Changes

Workflow Enhancements

• Added health-check job to ci.yml, frontend.yml, test-examples.yml that validates environment before running tests
• Enhanced error handling in build-push job with file existence checks and proper exit codes
• Structured logging with GitHub Actions annotations (::group::, ::notice::, ::error::)

- name: Pyroscope Build & push multi-arch image
  run: |
    set -euo pipefail
    echo "::group::Building multi-arch image"
    make docker-image/pyroscope/push-multiarch
    echo "::endgroup::"
- name: Get image metadata
  run: |
    if [ ! -f ./.docker-image-name-pyroscope ]; then
      echo "::error::Docker image name file not found"
      exit 1
    fi

Diagnostic Tooling

• Created .github/scripts/workflow-health-check.sh (290 lines) - validates Go 1.24.6+, Node 20+, Docker, network connectivity, runner compatibility
• Semantic version comparison for Go/Node version validation (not lexicographic)

MCP Server Integration

• Added .github/mcp-server-config.json for AI-assisted development with pyroscope-dev, github, and filesystem servers

Documentation

• .github/docs/WORKFLOW_TROUBLESHOOTING.md - covers startup issues, fork behavior, environment requirements, MCP setup
• .github/README.md - quick reference for CI/CD configuration
• Updated main README.md with workflow documentation links

Technical Notes

• Health checks use continue-on-error: true to avoid blocking on warnings
• Frontend build verification checks specific output directory (public/build per webpack config)
• Fork-compatible: workflows use runner fallbacks and conditional secrets access
• No breaking changes to existing workflow behavior

Original prompt

Problem Statement

The repository workflows are failing to start properly. Specific issues include:

1. MPC (Model Context Protocol) Integration: Code operations require proper MPC server configuration and integration for seamless workflow execution.

2. Linux Environment Setup: Workflows need proper Linux environment configuration including:

   • Correct package dependencies
   • Build tool installations
   • Environment variable setup

3. Networking Configuration: Network-related configurations (port bindings, service connections, container networking) need to be verified and corrected.

4. Issue Reference #100009: Address specific startup failures related to this issue.

Requirements

• Ensure all GitHub Actions workflows can start successfully
• Add proper MPC server configuration if needed
• Verify Linux dependencies and build tools are correctly specified
• Fix any networking issues in CI/CD pipelines
• Add error handling and logging for debugging startup issues
• Test that Go 1.24.9 and Node 20 environments work correctly
• Ensure compatibility with existing 15 workflows (ci.yml, frontend.yml, release workflows, etc.)

Success Criteria

• All workflows start without errors
• Build processes complete successfully
• Proper logging for troubleshooting
• Documentation of any new configuration requirements

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.