Separate org and user search

[SamMorrowDrums]

In order to make separation of certain objects more clear we should separate them. This means orgs and users are not the same.

A follow-up will be to separate issue and PR search by also scoping the queries and producing separate functions. It is best for the LLM that it has clear boundaries, and concepts are consistent, rather than accepting the legacy API quirks.

[Copilot]

Pull Request Overview

This PR separates organization searches from user searches by introducing dedicated tools and refactoring common logic.

• Registers a new orgs toolset in InitToolsets.
• Refactors search handlers with userOrOrgHandler and adds a (currently unused) minimalAccountSearchHandler.
• Implements SearchOrgs function and its tests in search_test.go.

Reviewed Changes

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

File	Description
pkg/github/tools.go	Added and registered "orgs" toolset alongside existing toolsets
pkg/github/search.go	Refactored search logic, added userOrOrgHandler, SearchOrgs, and residual minimalAccountSearchHandler
pkg/github/search_test.go	Added Test_SearchOrgs suite to validate organization search tool

Comments suppressed due to low confidence (3)

pkg/github/search.go:163

• The minimalAccountSearchHandler function is never used. Consider removing it or integrating it into the userOrOrgHandler to avoid dead code.

func minimalAccountSearchHandler(accountType string, query string, getClient GetClientFn, ctx context.Context, sort, order string, pagination PaginationParams) {

pkg/github/search.go:335

• [nitpick] The translation key TOOL_SEARCH_ORGS_USER_TITLE includes USER although this is for organizations; consider renaming it to TOOL_SEARCH_ORGS_TITLE for consistency.

mcp.WithToolAnnotation(mcp.ToolAnnotation{ Title: t("TOOL_SEARCH_ORGS_USER_TITLE", "Search organizations"),

pkg/github/search_test.go:521

• [nitpick] Tests for SearchOrgs cover the default pagination but don’t verify behavior when non-default sort, order, or pagination parameters are provided. Consider adding cases to cover those parameters.

requestArgs: map[string]interface{}{