Fix Serena MCP testing prompt in smoke tests

[Copilot]

Smoke test workflows were incorrectly instructing agents to use bash commands (go version) to test Serena integration instead of using Serena MCP server tools.

Changes

• smoke-copilot.md: Updated test requirement Lpcox/initial implementation #2 to use activate_project MCP tool
• smoke-codex.md: Updated test requirement Lpcox/initial implementation #2 to use activate_project MCP tool

Before/After

Before:

Use the serena-go tool to run a basic go command like "go version" to verify the tool is available

After:

Use the Serena MCP server tool `activate_project` to initialize the workspace and verify it succeeds (do NOT use bash to run go commands - use Serena's MCP tools)

This ensures smoke tests validate the MCP server integration correctly rather than testing Go toolchain availability via bash.

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:

• this-host-does-not-exist-12345.com
  • Triggering command: /tmp/go-build450283344/b278/mcp.test /tmp/go-build450283344/b278/mcp.test -test.testlogfile=/tmp/go-build450283344/b278/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true ortcfg (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)

---

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