Configure CI to trigger smoke-copilot, large-payload-tester, and language-support-tester workflows

[Claude]

Configures the CI workflow to automatically trigger three test workflows when changes are pushed to the main branch after all CI checks pass.

Changes

• Added three new CI jobs that trigger on main branch pushes after unit tests, linting, and integration tests complete:

  • smoke-copilot - Triggers comprehensive Copilot engine validation
  • large-payload-tester - Triggers MCP Gateway large payload handling tests
  • language-support-tester - Triggers Serena MCP server language support tests

• Implementation details:

  • Uses GitHub's workflow_dispatch API via actions/github-script@v7
  • Jobs depend on [unit-test, lint, integration-test] to ensure code quality
  • Conditional execution: if: github.event_name == 'push' && github.ref == 'refs/heads/main'
  • Grants actions: write permission to each job for workflow dispatch

smoke-copilot:
  runs-on: ubuntu-latest
  needs: [unit-test, lint, integration-test]
  if: github.event_name == 'push' && github.ref == 'refs/heads/main'
  permissions:
    actions: write
  steps:
    - name: Trigger smoke-copilot workflow
      uses: actions/github-script@v7
      with:
        script: |
          await github.rest.actions.createWorkflowDispatch({
            owner: context.repo.owner,
            repo: context.repo.repo,
            workflow_id: 'smoke-copilot.lock.yml',
            ref: 'main'
          });

This ensures comprehensive testing runs automatically on main branch updates while keeping PR builds fast.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• example.com
  • Triggering command: /tmp/go-build3556205850/b279/launcher.test /tmp/go-build3556205850/b279/launcher.test -test.testlogfile=/tmp/go-build3556205850/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true p/go-build -v 86_64/as --abbrev-ref 64/src/runtime/c-unsafeptr=false it ache/go/1.25.7/x/tmp/go-build3556205850/b165/vet.cfg -q ache/go/1.25.7/x64/src/runtime/c-c=4 ^system$ x_amd64/vet -e ^system$ /usr/bin/base64 x_amd64/vet (dns block)
• invalid-host-that-does-not-exist-12345.com
  • Triggering command: /tmp/go-build3556205850/b264/config.test /tmp/go-build3556205850/b264/config.test -test.testlogfile=/tmp/go-build3556205850/b264/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true 64/src/runtime/cgo 64/src/internal/synctest/synctes--64 64/bin/as --abbrev-ref HEAD .12/x64/git 07.o -c 64/src/runtime/cgo git x_amd64/compile --abbrev-ref /maps cal/bin/git x_amd64/compile (dns block)
• nonexistent.local
  • Triggering command: /tmp/go-build3556205850/b279/launcher.test /tmp/go-build3556205850/b279/launcher.test -test.testlogfile=/tmp/go-build3556205850/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true p/go-build -v 86_64/as --abbrev-ref 64/src/runtime/c-unsafeptr=false it ache/go/1.25.7/x/tmp/go-build3556205850/b165/vet.cfg -q ache/go/1.25.7/x64/src/runtime/c-c=4 ^system$ x_amd64/vet -e ^system$ /usr/bin/base64 x_amd64/vet (dns block)
• slow.example.com
  • Triggering command: /tmp/go-build3556205850/b279/launcher.test /tmp/go-build3556205850/b279/launcher.test -test.testlogfile=/tmp/go-build3556205850/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true p/go-build -v 86_64/as --abbrev-ref 64/src/runtime/c-unsafeptr=false it ache/go/1.25.7/x/tmp/go-build3556205850/b165/vet.cfg -q ache/go/1.25.7/x64/src/runtime/c-c=4 ^system$ x_amd64/vet -e ^system$ /usr/bin/base64 x_amd64/vet (dns block)
• this-host-does-not-exist-12345.com
  • Triggering command: /tmp/go-build3556205850/b288/mcp.test /tmp/go-build3556205850/b288/mcp.test -test.testlogfile=/tmp/go-build3556205850/b288/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true ache/go/1.25.7/x-errorsas BtCO/d-tAm9NIEjg-ifaceassert x_amd64/vet (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

Adds post-CI “fan-out” jobs to the main CI workflow so that, after core checks pass on main, three additional workflows are dispatched for deeper validation.

Changes:

• Added smoke-copilot, large-payload-tester, and language-support-tester jobs to .github/workflows/ci.yml.
• Each new job depends on unit-test, lint, and integration-test, and uses workflow_dispatch via actions/github-script.

Comments suppressed due to low confidence (2)

.github/workflows/ci.yml:166

• actions/github-script is referenced by tag (@v7) rather than being pinned to a specific commit SHA. Please pin to a commit SHA (consistent with the rest of ci.yml) to avoid mutable action tags.

      - name: Trigger large-payload-tester workflow
        uses: actions/github-script@v7
        with:

.github/workflows/ci.yml:185

• actions/github-script is referenced by tag (@v7) rather than being pinned to a specific commit SHA. Pinning the action (as done for checkout/setup-go in this workflow) improves supply-chain security and makes builds reproducible.

      - name: Trigger language-support-tester workflow
        uses: actions/github-script@v7
        with:

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

actions/github-script is referenced by tag (@v7) rather than being pinned to a specific commit SHA. This repo pins actions to SHAs elsewhere in this workflow, so this should be pinned as well to reduce supply-chain risk and ensure reproducible runs.

This issue also appears in the following locations of the same file:

• line 164
• line 183