tests: align conformance fixtures with @modelcontextprotocol/conformance main

The conformance suite's main branch (post 0.2.0-alpha.2) made two
breaking changes that our pinned wire-name / spec-version contracts had
to follow:

1. `DRAFT-2026-v1` wire literal flipped to `2026-07-28` (commit
   6f83abf in the conformance repo).
2. `incomplete-result-*` server scenarios renamed to
   `input-required-result-*` and extended from 8 to 14 scenarios
   (PR #262 in the conformance repo, follow-on to our own MRTR rename
   in PR #1458 where `IncompleteResult` became `InputRequiredResult`).

Track A (the published 0.2.0-alpha.2 pin) is unaffected and continues
to skip these tests via the wire-version-match gate introduced in
`f3698c71`. Track B (a private install of the conformance `main`
branch with the four merged sessionless/MRTR/error-code/tasks PRs)
now exercises 12 of the 14 MRTR scenarios end-to-end against this
SDK's `ConformanceServer`.

Changes in this commit:

- `IncompleteResultTools.cs` and `IncompleteResultPrompts.cs` —
  rename 6 tool wire names plus 1 prompt wire name from
  `test_incomplete_result_*` (and `test_tool_with_elicitation`)
  to `test_input_required_result_*` so the conformance scenarios
  can find them. The C# class names are intentionally left as
  `Incomplete*` to keep the diff minimal; the comment block above
  `RunMrtrConformanceTest` documents the asymmetry.
- `ServerConformanceTests.cs` — replace the 8-row MRTR theory with
  the 14-row theory matching the new conformance scenario set; flip
  the two `--spec-version DRAFT-2026-v1` references to
  `2026-07-28`; mark two scenarios skipped that require
  server-side patterns the `ConformanceServer` tools don't yet
  implement (HMAC-signed requestState for
  `input-required-result-tampered-state`; per-request capability
  gating for `input-required-result-capability-check`). Those
  scenarios are still feature-flagged behind the wire-version gate so
  they only attempt to run when the installed conformance package
  speaks `2026-07-28`.
- `CachingConformanceTests.cs` — flip the `--spec-version`
  reference and rewrite the doc remarks to explain the
  wire-version-match gate.

Validation: `dotnet test` over the targeted slice (5 conformance
test classes) under serial run reports 17 pass / 1 fail / 2 skip
against the private `compat/conformance-draft` build. The single
failure (`Sep2243.http-custom-headers`) is a pre-existing C# SDK
client bug exposed by the conformance-pin bump: the client sends no
`Mcp-Param-*` headers when the server's tool advertises
`x-mcp-header` annotations. The bug exists on `origin/main`
(`git diff origin/main..HEAD -- src/ModelContextProtocol.Core/Client`
on these files is empty) and is unrelated to the SEP-2575 / SEP-2567
draft work in this PR. Tracking as a follow-up.

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

Author: halter73

tests/ModelContextProtocol.AspNetCore.Tests/CachingConformanceTests.cs

@@ -105,12 +105,14 @@ public async ValueTask DisposeAsync()
 /// (tools/list, prompts/list, resources/list, resources/templates/list, resources/read).
 /// </summary>
 /// <remarks>
-/// The scenario is draft-only (introduced in DRAFT-2026-v1) and uses the stateless lifecycle.
-/// It is gated on the installed conformance package version (>= 0.2.0) and is skipped when
-/// running against the currently-pinned package, so it activates automatically once a
-/// conformance package containing the caching scenario is installed (including a local private
-/// build installed via <c>npm install --no-save &lt;path-to-conformance&gt;</c>). The stateless
-/// server is started only after the gates pass, so a skipped run binds no port.
+/// The scenario is draft-only (introduced in spec wire version 2026-07-28) and uses the
+/// stateless lifecycle. It is gated on the installed conformance package version (>= 0.2.0)
+/// AND on the installed package emitting the draft wire string this SDK speaks (so it stays
+/// skipped under conformance 0.2.0-alpha.2 which still ships the placeholder
+/// <c>DRAFT-2026-v1</c>). It activates automatically once a conformance package emitting
+/// <c>2026-07-28</c> is installed (e.g. via
+/// <c>npm install --no-save &lt;path-to-conformance&gt;</c>). The stateless server is
+/// started only after the gates pass, so a skipped run binds no port.
 /// </remarks>
 public class CachingConformanceTests(ITestOutputHelper output)
 {
@@ -128,7 +130,7 @@ public async Task RunCachingConformanceTest()
         // explicitly (and suppress the MCP_CONFORMANCE_PROTOCOL_VERSION override to avoid a
         // conflicting duplicate --spec-version flag).
         var result = await NodeHelpers.RunServerConformanceAsync(
-            $"server --url {server.ServerUrl} --scenario caching --spec-version DRAFT-2026-v1",
+            $"server --url {server.ServerUrl} --scenario caching --spec-version 2026-07-28",
             line => { try { output.WriteLine(line); } catch { } },
             appendProtocolVersionFromEnv: false,
             cancellationToken: TestContext.Current.CancellationToken);

tests/ModelContextProtocol.AspNetCore.Tests/ServerConformanceTests.cs

@@ -143,15 +143,15 @@ public async Task RunConformanceTest_HttpHeaderValidation()
             !NodeHelpers.HasSep2243Scenarios(),
             "SEP-2243 conformance scenarios not available (requires conformance package >= 0.2.0).");
 
-        // SEP-2243 is a draft (DRAFT-2026-v1) scenario that uses the stateless lifecycle, so it
+        // SEP-2243 is a draft (2026-07-28) scenario that uses the stateless lifecycle, so it
         // requires a stateless server (a stateful server rejects the un-initialized list/call
         // requests with JSON-RPC -32000). Use a dedicated port range so it never collides with
         // the stateful class fixture (300x) or the caching stateless server (301x).
         await using var server = await StatelessConformanceServer.StartAsync(
             TestContext.Current.CancellationToken, basePort: 3021);
 
         var result = await RunStatelessConformanceTestAsync(
-            $"server --url {server.ServerUrl} --scenario http-header-validation --spec-version DRAFT-2026-v1");
+            $"server --url {server.ServerUrl} --scenario http-header-validation --spec-version 2026-07-28");
 
         Assert.True(result.Success,
             $"Conformance test failed.\n\nStdout:\n{result.Output}\n\nStderr:\n{result.Error}");
@@ -169,32 +169,49 @@ public async Task RunConformanceTest_HttpCustomHeaderServerValidation()
             TestContext.Current.CancellationToken, basePort: 3024);
 
         var result = await RunStatelessConformanceTestAsync(
-            $"server --url {server.ServerUrl} --scenario http-custom-header-server-validation --spec-version DRAFT-2026-v1");
+            $"server --url {server.ServerUrl} --scenario http-custom-header-server-validation --spec-version 2026-07-28");
 
         Assert.True(result.Success,
             $"Conformance test failed.\n\nStdout:\n{result.Output}\n\nStderr:\n{result.Error}");
     }
 
-    // SEP-2322 (Multi Round-Trip Requests / IncompleteResult) conformance scenarios.
+    // SEP-2322 (Multi Round-Trip Requests / InputRequiredResult) conformance scenarios.
     // The csharp-sdk ConformanceServer surfaces the matching tools/prompts via
-    // ConformanceServer.Tools.IncompleteResultTools and ConformanceServer.Prompts.IncompleteResultPrompts.
+    // ConformanceServer.Tools.IncompleteResultTools and ConformanceServer.Prompts.IncompleteResultPrompts
+    // (the class names predate the conformance-suite rename from "incomplete-result-*" to
+    // "input-required-result-*"; the wire-level tool names now match the new convention).
     // Each scenario uses the conformance harness's RawMcpSession, which negotiates 2026-07-28
     // so the csharp-sdk emits InputRequiredResult on the wire. These tests skip until the
-    // upstream conformance package ships with SEP-2322 scenarios
-    // (https://github.com/modelcontextprotocol/conformance/pull/188).
+    // installed conformance package ships SEP-2322 scenarios <em>and</em> emits this SDK's
+    // draft wire string (see <see cref="NodeHelpers.HasMrtrScenarios"/>).
+    //
+    // Two scenarios (input-required-result-tampered-state and input-required-result-capability-check)
+    // require advanced server-side logic not yet built into the ConformanceServer:
+    //   - tampered-state: HMAC integrity protection on requestState. Server-implementer concern
+    //     outside the SDK wire surface; would need a sample tool implementing the pattern.
+    //   - capability-check: per-request reading of clientCapabilities to gate which inputRequests
+    //     are returned. SDK exposes capabilities via JsonRpcMessageContext but no current tool
+    //     conditionally emits inputRequests based on them.
+    // These rows are skipped until matching tool implementations are added.
     [Theory]
-    [InlineData("incomplete-result-basic-elicitation")]
-    [InlineData("incomplete-result-basic-sampling")]
-    [InlineData("incomplete-result-basic-list-roots")]
-    [InlineData("incomplete-result-request-state")]
-    [InlineData("incomplete-result-multiple-input-requests")]
-    [InlineData("incomplete-result-multi-round")]
-    [InlineData("incomplete-result-missing-input-response")]
-    [InlineData("incomplete-result-non-tool-request")]
+    [InlineData("input-required-result-basic-elicitation")]
+    [InlineData("input-required-result-basic-sampling")]
+    [InlineData("input-required-result-basic-list-roots")]
+    [InlineData("input-required-result-request-state")]
+    [InlineData("input-required-result-multiple-input-requests")]
+    [InlineData("input-required-result-multi-round")]
+    [InlineData("input-required-result-missing-input-response")]
+    [InlineData("input-required-result-non-tool-request")]
+    [InlineData("input-required-result-result-type")]
+    [InlineData("input-required-result-unsupported-methods")]
+    [InlineData("input-required-result-tampered-state", Skip = "Requires HMAC-protected requestState pattern in ConformanceServer tools (not yet implemented).")]
+    [InlineData("input-required-result-capability-check", Skip = "Requires per-request capability-aware inputRequest gating in ConformanceServer tools (not yet implemented).")]
+    [InlineData("input-required-result-ignore-extra-params")]
+    [InlineData("input-required-result-validate-input")]
     public async Task RunMrtrConformanceTest(string scenario)
     {
         Assert.SkipWhen(!NodeHelpers.IsNodeInstalled(), "Node.js is not installed. Skipping conformance tests.");
-        Assert.SkipWhen(!NodeHelpers.HasMrtrScenarios(), "SEP-2322 MRTR conformance scenarios not yet available in the published @modelcontextprotocol/conformance package.");
+        Assert.SkipWhen(!NodeHelpers.HasMrtrScenarios(), "SEP-2322 MRTR conformance scenarios not yet available in the published @modelcontextprotocol/conformance package (or installed version uses a stale draft wire string).");
 
         var result = await RunConformanceTestsAsync(
             $"server --url {fixture.ServerUrl} --scenario {scenario}");

tests/ModelContextProtocol.ConformanceServer/Prompts/IncompleteResultPrompts.cs

@@ -16,8 +16,8 @@ namespace ConformanceServer.Prompts;
 [McpServerPromptType]
 public sealed class IncompleteResultPrompts
 {
-    [McpServerPrompt(Name = "test_incomplete_result_prompt")]
-    [Description("SEP-2322 D1: prompts/get returns IncompleteResult until user_context is supplied.")]
+    [McpServerPrompt(Name = "test_input_required_result_prompt")]
+    [Description("SEP-2322 D1: prompts/get returns InputRequiredResult until user_context is supplied.")]
     public static GetPromptResult IncompleteResultPrompt(RequestContext<GetPromptRequestParams> context)
     {
         if (context.Params!.InputResponses is { } responses &&

tests/ModelContextProtocol.ConformanceServer/Tools/IncompleteResultTools.cs

@@ -20,8 +20,8 @@ namespace ConformanceServer.Tools;
 public sealed class IncompleteResultTools
 {
     // ──── A1: Basic Elicitation ─────────────────────────────────────────────
-    [McpServerTool(Name = "test_tool_with_elicitation")]
-    [Description("SEP-2322 A1: returns IncompleteResult with elicitation/create keyed 'user_name'.")]
+    [McpServerTool(Name = "test_input_required_result_elicitation")]
+    [Description("SEP-2322 A1: returns InputRequiredResult with elicitation/create keyed 'user_name'.")]
     public static CallToolResult ToolWithElicitation(RequestContext<CallToolRequestParams> context)
     {
         if (context.Params!.InputResponses is { } responses &&
@@ -51,8 +51,8 @@ public static CallToolResult ToolWithElicitation(RequestContext<CallToolRequestP
     }
 
     // ──── A2: Basic Sampling ────────────────────────────────────────────────
-    [McpServerTool(Name = "test_incomplete_result_sampling")]
-    [Description("SEP-2322 A2: returns IncompleteResult with sampling/createMessage keyed 'capital_question'.")]
+    [McpServerTool(Name = "test_input_required_result_sampling")]
+    [Description("SEP-2322 A2: returns InputRequiredResult with sampling/createMessage keyed 'capital_question'.")]
     public static CallToolResult ToolWithSampling(RequestContext<CallToolRequestParams> context)
     {
         if (context.Params!.InputResponses is { } responses &&
@@ -81,8 +81,8 @@ public static CallToolResult ToolWithSampling(RequestContext<CallToolRequestPara
     }
 
     // ──── A3: Basic ListRoots ───────────────────────────────────────────────
-    [McpServerTool(Name = "test_incomplete_result_list_roots")]
-    [Description("SEP-2322 A3: returns IncompleteResult with roots/list keyed 'client_roots'.")]
+    [McpServerTool(Name = "test_input_required_result_list_roots")]
+    [Description("SEP-2322 A3: returns InputRequiredResult with roots/list keyed 'client_roots'.")]
     public static CallToolResult ToolWithListRoots(RequestContext<CallToolRequestParams> context)
     {
         if (context.Params!.InputResponses is { } responses &&
@@ -102,7 +102,7 @@ public static CallToolResult ToolWithListRoots(RequestContext<CallToolRequestPar
     // ──── B1: requestState round-trip ───────────────────────────────────────
     private const string RequestStateToken = "mrtr-conformance-state-v1";
 
-    [McpServerTool(Name = "test_incomplete_result_request_state")]
+    [McpServerTool(Name = "test_input_required_result_request_state")]
     [Description("SEP-2322 B1: round-trips a requestState string; R2 echoes 'state-ok' on success.")]
     public static CallToolResult ToolWithRequestState(RequestContext<CallToolRequestParams> context)
     {
@@ -135,7 +135,7 @@ public static CallToolResult ToolWithRequestState(RequestContext<CallToolRequest
     }
 
     // ──── B2: Multiple input requests in one round ──────────────────────────
-    [McpServerTool(Name = "test_incomplete_result_multiple_inputs")]
+    [McpServerTool(Name = "test_input_required_result_multiple_inputs")]
     [Description("SEP-2322 B2: returns 3 simultaneous inputRequests (elicit + sampling + roots) plus requestState.")]
     public static CallToolResult ToolWithMultipleInputs(RequestContext<CallToolRequestParams> context)
     {
@@ -177,7 +177,7 @@ public static CallToolResult ToolWithMultipleInputs(RequestContext<CallToolReque
     }
 
     // ──── B3: Multi-round (R1 -> incomplete, R2 -> incomplete (new state), R3 -> complete) ─────
-    [McpServerTool(Name = "test_incomplete_result_multi_round")]
+    [McpServerTool(Name = "test_input_required_result_multi_round")]
     [Description("SEP-2322 B3: three-round flow whose requestState changes between rounds.")]
     public static CallToolResult ToolWithMultiRound(RequestContext<CallToolRequestParams> context)
     {