feat: make projects toolset a default toolset

[yani-]

Summary

• Mark ToolsetMetadataProjects with Default: true so that the projects toolset (projects_list, projects_get, projects_write) is included in the default toolset configuration.
• Update test assertions in tools_test.go to account for the new default.

Motivation

The projects toolset is fully implemented but not included in defaults. Users connecting via the remote MCP server (https://api.githubcopilot.com/mcp/) or Claude Desktop's URL connector have no access to GitHub Projects v2 tools unless they explicitly configure the toolset via /x/projects URL path or X-MCP-Toolsets header.

The README advertises project board management as a feature ("Let AI help triage bugs, review code changes, and maintain project boards"), but the tools are not available out of the box. Claude Desktop's connector UI does not support custom headers or URL path modifiers, so users of that flow have no practical way to enable the projects toolset without switching to a local stdio setup.

The toolset adds only 3 tools, so the impact on the default tool count is minimal.

Closes #2275

Test plan

• UPDATE_TOOLSNAPS=true go test ./... — all tests pass
• script/lint — 0 issues
• script/generate-docs — no doc changes needed (projects toolset already documented)

[Copilot]

Pull request overview

This PR updates the GitHub MCP Server’s default toolset selection so that the existing projects toolset (GitHub Projects v2 tools) is enabled by default, aligning the out-of-the-box tool availability with advertised capabilities and improving usability for connector flows that can’t customize toolsets.

Changes:

• Mark ToolsetMetadataProjects as Default: true so it’s included when default toolsets are used.
• Update TestAddDefaultToolset expectations to include projects in the expanded default toolset list.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
pkg/github/tools.go	Adds Default: true to the Projects toolset metadata so it becomes part of the default toolset configuration.
pkg/github/tools_test.go	Updates default toolset expansion test cases to include the projects toolset.

[yani-]

Thanks for the explanation — that makes sense. Closing this as the token cost tradeoff is a valid reason to keep the default toolset minimal.

For anyone landing here with the same problem: you can enable the projects toolset by running the local server with --toolsets=default,projects and a personal access token, or by using the /x/projects URL path as a second connector.