Add optional rationale parameter to update_issue_type tool

[alondahari]

Summary

Adds an optional rationale string parameter (max 280 chars) to the update_issue_type MCP tool, enabling agents to explain their classification decisions when setting an issue's type.

Motivation

Per the decision update on github/plan-track-agentic-toolkit#57, we're adding rationale directly to the upstream tool rather than as a remote-server-only override. This keeps the open-source tool schema in sync with the API contract while the API gracefully ignores the rationale when the server-side feature flag is disabled.

Why a standalone tool instead of using issueUpdateTool

The issueUpdateTool helper constrains handlers to returning a *github.IssueRequest, which only supports Type *string. When rationale is provided, the REST API expects the type field as an object ({"value": "...", "rationale": "..."}) rather than a plain string. Since go-github's IssueRequest struct can't represent this object form, we need to build a custom request body and use client.NewRequest/client.Do directly. Breaking out of the helper is the minimal change that enables the two serialization paths (string when no rationale, object when rationale is present) without modifying the shared helper or other tools that depend on it.

Once the API changes are stable and go-github is updated to support the object form natively, we intend to migrate this tool back to the shared issueUpdateTool helper.

Changes

• pkg/github/issues_granular.go — Rewrote GranularUpdateIssueType as a standalone tool (no longer uses issueUpdateTool helper). When rationale is provided, sends the type as an object {"value": "...", "rationale": "..."} via a raw PATCH request. When omitted, sends {"type": "..."} preserving existing behavior.
• pkg/github/granular_tools_test.go — Expanded test to table-driven covering both type-only and type-with-rationale cases.
• pkg/github/__toolsnaps__/update_issue_type.snap — Updated schema snapshot.

Acceptance criteria

• ✅ rationale is always in the schema (no feature-flag gating in this repo)
• ✅ No behavioral change when rationale is omitted
• ✅ Single API call passes both type and rationale when provided

Closes github/plan-track-agentic-toolkit#57

/cc @margaretmz

[Copilot]

Pull request overview

Adds an optional rationale parameter to the update_issue_type granular MCP tool so agents can provide a short explanation when setting an issue’s type, while preserving the existing request shape when rationale is omitted.

Changes:

• Reworked update_issue_type to send either a string type field (no rationale) or an object type field with {value, rationale} (when rationale is present).
• Expanded unit test coverage to validate both request payload shapes.
• Updated the tool schema snapshot to include the new optional rationale field (maxLength 280).

Show a summary per file

File	Description
pkg/github/issues_granular.go	Reimplements update_issue_type as a standalone tool and adds request-body branching to support sending rationale.
pkg/github/granular_tools_test.go	Adds table-driven tests to assert the outgoing PATCH body for type-only vs type-with-rationale.
pkg/github/toolsnaps/update_issue_type.snap	Updates the tool input schema snapshot to include the optional rationale parameter.

Copilot's findings

• Files reviewed: 3/3 changed files
• Comments generated: 2

[Copilot]

Addressed in 5cfd36a.

[Copilot]

Addressed in 5cfd36a.