feat(issues): add protocol-gated typed consolidated issue tools (#3393)

* feat(repos): complete typed repository tool outputs

Migrate the remaining 17 repository tools to concrete inputs and outputs. Preserve existing content, mutations, scopes, filtering, and protocol gating; add wire and schema conformance coverage.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* chore(repos): exclude unrelated snapshot formatting drift

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* refactor(repos): compact typed repository outputs

Replace raw REST output schemas with compact repository DTOs, retain one canonical snapshot per tool, and align modern JSON text with structured output while pinning legacy content.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* feat(issues): add typed consolidated issue tool contracts

Preserve raw helper APIs and exact legacy text while exposing concrete output unions for modern protocols. Retain explicit awaiting statuses and real null responses without exposing SDK-generated error fallbacks.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* chore: regenerate license files

Auto-generated by license-check workflow

* refactor(issues): minimize consolidated typed outputs

Project compact method-discriminated DTOs from API responses while preserving the separate legacy text formatter and explicit app-awaiting status. Cache strict schemas and keep only canonical snapshots. Strengthen null-member presence, schema size, and lockdown projection regressions.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* fix(issues): keep union property schemas portable

Preserve forbidden variant properties as annotated schema objects rather than boolean schemas emitted by jsonschema-go. Cover Inspector's input paths and IFC labels on every issue-read method across protocols.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* test(issues): cover strict sub-issue output variants

Reject unknown methods, states, field types, opaque values and API URL properties while covering nullable and empty method data.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* test(issues): pin compact comment user redaction

Pin unchanged legacy profile/avatar fields separately from compact modern user projections and assert identical lockdown filtering and sanitization across protocols.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* fix(issues): restore main-identical advertised input schema

Remove added custom-field union constraints and sentinel enums from the advertised issue-write input. Preserve runtime exactly-one validation and private strict-schema tests. All three scoped input schemas compare exactly equal to main.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* fix(issues): restore protocol output parity

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* chore: regenerate license files

Auto-generated by license-check workflow

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: 3 people

docs/error-handling.md

@@ -57,6 +57,29 @@ This function:
 return ghErrors.NewGitHubGraphQLErrorResponse(ctx, message, err), nil
 ```
 
+### Typed Tool Results
+
+Tools registered with concrete `NewTool[In, Out]` types expose output schemas and
+`structuredContent` only when the negotiated protocol is `2026-07-28` or newer.
+Older or unknown protocols retain the original text responses without these
+typed-output additions. Ordinary API and validation errors never expose the
+SDK-generated zero-value structured output.
+
+Handler-provided structured statuses are distinct from generated error output.
+For example, `issue_write` can return `IsError: true` with
+`status: "awaiting_user_submission"` while an MCP App form is pending. Modern
+clients retain that explicit status and its reason; legacy clients retain the
+stop message and error flag without structured content. This status does not
+mean the issue was created or updated. The output schema includes a strict
+status variant alongside the mutation's `id`/`url` variant. Multi-round-trip
+`InputRequests` continue to pass through unchanged.
+
+The consolidated issue tools use method-discriminated object outputs for modern
+successes. Issue and comment data are projected from the API responses into
+compact DTOs, excluding API, node, and hypermedia URLs while retaining human
+links. Legacy text is marshalled separately and keeps its original format and
+fields.
+
 ### Context Management
 
 The error handling system uses context to store errors for later inspection: