Verify mcp-server binary resolution after repository migration

[Copilot]

Reviewed mcp-server command and gh-aw binary resolution logic following the repository move from githubnext/gh-aw to github/gh-aw. The migration is already complete - no code changes required.

Verified Components

• MCP server binary resolution (pkg/cli/mcp_server.go)
  Uses workflow.ExecGHContext() → gh aw commands, automatically resolved by gh CLI regardless of installation source

• Binary discovery (pkg/workflow/mcp_setup_generator.go)

  gh extension install github/gh-aw  # Line 181 - correct
  GH_AW_BIN=$(which gh-aw || find ~/.local/share/gh/extensions/gh-aw ...)  # Works with both sources

• Error messages and documentation
  All references in mcp_validation.go, update_extension_check.go, and update_check.go correctly use github/gh-aw

• Migration codemod (pkg/cli/codemod_install_script_url.go)
  Existing tool automatically migrates workflow files from githubnext → github references

Remaining githubnext References (Intentional)

• githubnext/agentics - separate workflow catalog repository
• Codemod and test files - need to reference old location for migration logic
• Campaign template project URL - may still be in githubnext org

Original prompt

Review the mcp-server command and the logic to resolve the location of the gh-aw binary. The project location changed from githubnext/gh-aw to github/aw

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.