fix(showcase): close 2 D5 fixture gaps + filter deprecated features from gold-standard view

Three fixes that follow up on PR CopilotKit#4743 to bring LGP closer to fully-green
on the dashboard:

1. tool-rendering-reasoning-chain probe: was failing with
   `expected [data-testid="reasoning-block"] to mount within 30000ms`.
   Root cause: the demo's `<ReasoningBlock>` slot only mounts when a
   reasoning-role message lands in the transcript, which requires
   aimock to emit REASONING_MESSAGE_* events, which in turn requires
   the fixture's first-leg response to carry a `reasoning` field. The
   weather/Tokyo and SFO/JFK first-leg fixtures were missing it.
   Mirrors the convention documented in reasoning-display.json:2.
   Patched both source (harness/fixtures/d5/) and bundle (aimock/d5-all.json).

2. gen-ui-interrupt source fixture: the source fixture file was missing
   the resume-leg toolCallId entries that already existed in the bundle.
   Cosmetic mirror so re-bundling stays consistent. Same chip prompts +
   same toolCallIds as interrupt-headless.json (both probes share the
   same agent and aimock fixture set; the difference is the FRONTEND
   rendering — useInterrupt inline vs useHeadlessInterrupt separate-pane).

3. Dashboard gold-standard filter: 4 deprecated/legacy features
   (agentic-chat-reasoning, hitl, hitl-in-chat-booking,
   reasoning-default-render) used to render as X-marked rows in the
   LGP gold-standard dashboard view because LGP intentionally does
   NOT implement them — they were consolidated into the modern shape
   (reasoning-custom + reasoning-default; hitl-in-chat with
   useHumanInTheLoop). Other 17 integrations still serve those legacy
   demos, so we don't yank the features from feature-registry.json
   entirely. Instead: marked them `deprecated: true` and updated
   generate-registry.ts to skip emitting cells when a deprecated
   feature is unshipped for an integration. LGP cells: 43 → 39 (the
   4 deprecated rows disappear). Other integrations: unchanged
   (audit trail preserved). Catalog total: 774 → 770.

Tests:
  - 1588/1588 harness vitest passing
  - 19/19 generate-catalog + generate-registry tests passing
    (counts updated for the 4 dropped LGP cells + new deprecated-
    feature filter test)
  - validate-fixture-tool-surface clean (282 fixtures × 627 demos)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: tylerslaton

showcase/aimock/d5-all.json

@@ -159,7 +159,8 @@
             "name": "search_flights",
             "arguments": "{\"origin\":\"SFO\",\"destination\":\"JFK\"}"
           }
-        ]
+        ],
+        "reasoning": "The user wants flights from SFO to JFK. I'll call search_flights with those airports to look up options."
       }
     },
     {
@@ -1192,7 +1193,8 @@
             "name": "get_weather",
             "arguments": "{\"location\":\"Tokyo\"}"
           }
-        ]
+        ],
+        "reasoning": "The user asked about Tokyo weather. I'll call get_weather with location='Tokyo' to get the current conditions."
       }
     },
     {
@@ -1209,7 +1211,8 @@
             "name": "get-weather",
             "arguments": "{\"location\":\"Tokyo\"}"
           }
-        ]
+        ],
+        "reasoning": "The user asked about Tokyo weather. I'll call get_weather with location='Tokyo' to get the current conditions."
       }
     },
     {

showcase/harness/fixtures/d5/gen-ui-interrupt.json

@@ -1,12 +1,16 @@
 {
-  "_comment": "D5 fixture for /demos/gen-ui-interrupt. Two pill prompts (sales call / 1:1 with Alice). Each triggers the `schedule_meeting` tool which raises a LangGraph interrupt; the frontend renders the time picker, the user picks, and the agent resumes with a confirmation message.",
+  "_comment": "D5 fixture for /demos/gen-ui-interrupt. Two pill prompts (sales call / 1:1 with Alice). Each pill is a 2-leg flow — first leg returns a `schedule_meeting` tool call (which triggers the Python agent's `interrupt(...)` suspension); second leg matches `toolCallId` after the user picks a slot and returns a confirmation narration. Both legs are SHARED with /demos/interrupt-headless.json (same agent, same chip prompts, different frontend rendering — `useInterrupt` inline vs `useHeadlessInterrupt` in a separate pane). The `call_d5_schedule_sales_001` / `_alice_001` toolCallIds match `interrupt-headless.json` and `showcase/aimock/d5-all.json` so all three sources stay in lockstep.",
   "fixtures": [
     {
-      "match": { "userMessage": "intro call with the sales team" },
+      "match": {
+        "userMessage": "intro call with the sales team",
+        "toolName": "schedule_meeting"
+      },
       "response": {
         "content": "Sure — let me check available times.",
         "toolCalls": [
           {
+            "id": "call_d5_schedule_sales_001",
             "name": "schedule_meeting",
             "arguments": {
               "topic": "Sales intro call",
@@ -21,11 +25,24 @@
       }
     },
     {
-      "match": { "userMessage": "1:1 with Alice" },
+      "match": {
+        "userMessage": "intro call with the sales team",
+        "toolCallId": "call_d5_schedule_sales_001"
+      },
+      "response": {
+        "content": "Booked: Sales intro call confirmed for the slot you picked."
+      }
+    },
+    {
+      "match": {
+        "userMessage": "1:1 with Alice",
+        "toolName": "schedule_meeting"
+      },
       "response": {
         "content": "Got it — pulling up next-week slots.",
         "toolCalls": [
           {
+            "id": "call_d5_schedule_alice_001",
             "name": "schedule_meeting",
             "arguments": {
               "topic": "1:1 with Alice — Q2 goals",
@@ -40,15 +57,12 @@
       }
     },
     {
-      "match": { "userMessage": "request the gen-ui interrupt" },
-      "response": {
-        "content": "Choose to continue."
-      }
-    },
-    {
-      "match": { "userMessage": "confirm the gen-ui choice" },
+      "match": {
+        "userMessage": "1:1 with Alice",
+        "toolCallId": "call_d5_schedule_alice_001"
+      },
       "response": {
-        "content": "Gen-UI interrupt resolved."
+        "content": "Scheduled: 1:1 with Alice locked in for the slot you picked."
       }
     }
   ]

showcase/harness/fixtures/d5/tool-rendering-reasoning-chain.json

@@ -1,5 +1,5 @@
 {
-  "_comment": "D5 fixture for /demos/tool-rendering-reasoning-chain (LangGraph Python). The demo composes a reasoningMessage slot (<ReasoningBlock>) with per-tool renderers (WeatherCard / FlightListCard). Two chip prompts probed: 'What's the weather in Tokyo?' and 'Find flights from SFO to JFK.' — each is a 2-leg flow: first leg emits the tool call (get_weather / search_flights), second leg matches `hasToolResult: true` and emits the deterministic narration. The reasoning tokens themselves come from the agent's `init_chat_model(reasoning={effort:'low'})` — they're produced upstream of these fixtures (the LLM call returns the tool decision; reasoning lives in the same LLM payload). Mirrored verbatim into showcase/aimock/d5-all.json so re-bundling stays consistent.",
+  "_comment": "D5 fixture for /demos/tool-rendering-reasoning-chain (LangGraph Python). The demo composes a reasoningMessage slot (<ReasoningBlock data-testid=\"reasoning-block\">) with per-tool renderers (WeatherCard / FlightListCard). Two chip prompts probed: 'What's the weather in Tokyo?' and 'Find flights from SFO to JFK.' — each is a 2-leg flow: first leg emits the tool call (get_weather / search_flights) AND a `reasoning` field so aimock emits REASONING_MESSAGE_* events (role='reasoning'); without the reasoning field the v2 <ReasoningBlock> never mounts (mirrors the convention documented in reasoning-display.json). Second leg matches `hasToolResult: true` and emits the deterministic narration. The agent uses `init_chat_model(... use_responses_api=True, reasoning={effort:'low'})` — Responses-API mode delivers reasoning summaries alongside tool calls. Mirrored verbatim into showcase/aimock/d5-all.json so re-bundling stays consistent.",
   "fixtures": [
     {
       "match": {
@@ -8,6 +8,7 @@
         "toolName": "get_weather"
       },
       "response": {
+        "reasoning": "The user asked about Tokyo weather. I'll call get_weather with location='Tokyo' to get the current conditions.",
         "toolCalls": [
           {
             "id": "call_d5_get_weather_001",
@@ -32,6 +33,7 @@
         "hasToolResult": false
       },
       "response": {
+        "reasoning": "The user wants flights from SFO to JFK. I'll call search_flights with those airports to look up options.",
         "toolCalls": [
           {
             "id": "call_tr_flights_sfo_jfk_001",

showcase/scripts/__tests__/generate-catalog.test.ts

@@ -109,15 +109,22 @@ describe("Catalog Generator", () => {
       (c: any) => c.manifestation === "starter",
     );
 
-    expect(integrated.length).toBe(774); // 43 features x 18 integrations
+    // 43 features x 18 integrations = 774 nominal, but 4 deprecated
+    // features (agentic-chat-reasoning, hitl, hitl-in-chat-booking,
+    // reasoning-default-render) are filtered when an integration's
+    // manifest doesn't declare them — see deprecatedFeatureIds in
+    // generate-registry.ts. LGP doesn't declare any of the 4 (gold-
+    // standard reference uses the modern shape), so 4 LGP cells are
+    // dropped: 774 - 4 = 770.
+    expect(integrated.length).toBe(770);
     expect(starters.length).toBe(0);
-    expect(catalog.cells.length).toBe(774);
+    expect(catalog.cells.length).toBe(770);
     // total_cells excludes docs-only features (currently 1 feature x 18 integrations = 18)
-    expect(catalog.metadata.total_cells).toBe(756);
+    expect(catalog.metadata.total_cells).toBe(752);
     expect(catalog.metadata.docs_only).toBe(18);
   });
 
-  it("LGP has 43 cells: 38 wired + 1 stub + 4 unshipped", () => {
+  it("LGP has 39 cells: 38 wired + 1 stub (deprecated features filtered)", () => {
     runGenerator();
     const catalog = readCatalog();
 
@@ -126,15 +133,50 @@ describe("Catalog Generator", () => {
         c.integration === "langgraph-python" &&
         c.manifestation === "integrated",
     );
-    expect(lgpCells.length).toBe(43); // One cell per feature
+    // 39 = 39 features in LGP manifest (the 4 deprecated features are
+    // filtered out at catalog-generation time since LGP doesn't declare
+    // them — see deprecatedFeatureIds in generate-registry.ts).
+    expect(lgpCells.length).toBe(39);
 
     const wired = lgpCells.filter((c: any) => c.status === "wired");
     const stub = lgpCells.filter((c: any) => c.status === "stub");
     const unshipped = lgpCells.filter((c: any) => c.status === "unshipped");
 
     expect(wired.length).toBe(38);
     expect(stub.length).toBe(1);
-    expect(unshipped.length).toBe(4);
+    expect(unshipped.length).toBe(0);
+  });
+
+  it("deprecated features are emitted only for integrations that declare them", () => {
+    runGenerator();
+    const catalog = readCatalog();
+
+    // 4 features marked deprecated:true in feature-registry.json. LGP
+    // doesn't declare any of them (modern-shape reference); other
+    // integrations that DO declare them still get a cell so the
+    // cross-integration audit trail is preserved.
+    const deprecated = [
+      "agentic-chat-reasoning",
+      "hitl",
+      "hitl-in-chat-booking",
+      "reasoning-default-render",
+    ];
+
+    for (const feat of deprecated) {
+      const lgpCell = catalog.cells.find(
+        (c: any) =>
+          c.integration === "langgraph-python" && c.feature === feat,
+      );
+      expect(lgpCell).toBeUndefined();
+    }
+
+    // ag2 declares agentic-chat-reasoning + hitl + reasoning-default-render
+    // (per its manifest), so those cells exist.
+    const ag2Acr = catalog.cells.find(
+      (c: any) =>
+        c.integration === "ag2" && c.feature === "agentic-chat-reasoning",
+    );
+    expect(ag2Acr).toBeDefined();
   });
 
   it("stub detection: LGP/cli-start has stub status (demo exists, no route)", () => {
@@ -196,8 +238,10 @@ describe("Catalog Generator", () => {
     const catalog = readCatalog();
 
     expect(catalog.metadata).toBeDefined();
-    // total_cells excludes docs-only features
-    expect(catalog.metadata.total_cells).toBe(756);
+    // total_cells excludes docs-only features (and deprecated-feature cells
+    // that were filtered during catalog generation when an integration
+    // didn't declare them).
+    expect(catalog.metadata.total_cells).toBe(752);
 
     // Headline counts exclude docs-only cells; must sum to total_cells.
     expect(

showcase/scripts/generate-registry.ts

@@ -279,6 +279,7 @@ function generateCatalog(
       name: string;
       category: string;
       kind?: string;
+      deprecated?: boolean;
     }>;
     categories: Array<{ id: string; name: string }>;
   },
@@ -314,6 +315,21 @@ function generateCatalog(
       .map((f) => f.id),
   );
 
+  // Deprecated features — consolidated/replaced patterns that LGP (the
+  // gold-standard reference integration) intentionally does NOT implement,
+  // but legacy integrations still serve. We only EMIT a cell for a
+  // deprecated feature when the integration's manifest actively declares
+  // it; integrations that don't claim it (notably the gold-standard
+  // reference) get no row at all, so the dashboard's gold-standard view
+  // doesn't render confusing X-marked rows for patterns LGP intentionally
+  // skipped. The cross-integration audit trail is preserved on the
+  // integrations that DO declare the feature.
+  const deprecatedFeatureIds = new Set(
+    featureRegistry.features
+      .filter((f) => f.deprecated === true)
+      .map((f) => f.id),
+  );
+
   // Step 1: Cross-join to produce integrated cells and collect wired features
   // and unsupported features per integration.
   const wiredFeaturesPerIntegration = new Map<string, Set<string>>();
@@ -328,6 +344,17 @@ function generateCatalog(
 
     for (const featureId of allFeatureIds) {
       const status = determineCellStatus(featureId, integration);
+
+      // Deprecated-feature filter: skip emitting the cell entirely when
+      // the feature is deprecated AND this integration's manifest does
+      // NOT declare it. The cell would otherwise render as an
+      // unshipped/X row that's misleading — it implies LGP is missing
+      // something it intentionally doesn't have. Integrations that DO
+      // declare the deprecated feature still get their row (audit trail).
+      if (deprecatedFeatureIds.has(featureId) && status === "unshipped") {
+        continue;
+      }
+
       if (status === "wired") {
         wiredFeatures.add(featureId);
       }

showcase/shared/feature-registry.json

@@ -153,7 +153,8 @@
       "description": "Time-picker card rendered inline via useHumanInTheLoop for a booking flow",
       "kind": "primary",
       "og_docs_url": "https://docs.copilotkit.ai/generative-ui/your-components/interactive",
-      "shell_docs_path": "/generative-ui/your-components/interactive"
+      "shell_docs_path": "/generative-ui/your-components/interactive",
+      "deprecated": true
     },
     {
       "id": "hitl",
@@ -162,7 +163,8 @@
       "description": "Original HITL demo kept for backwards compatibility",
       "kind": "primary",
       "og_docs_url": "https://docs.copilotkit.ai/generative-ui/your-components/interactive",
-      "shell_docs_path": "/generative-ui/your-components/interactive"
+      "shell_docs_path": "/generative-ui/your-components/interactive",
+      "deprecated": true
     },
     {
       "id": "interrupt-headless",
@@ -254,7 +256,8 @@
       "category": "operational-generative-ui",
       "description": "Visible reasoning/thinking chain alongside the final answer",
       "og_docs_url": "https://docs.copilotkit.ai/custom-look-and-feel/reasoning-messages",
-      "shell_docs_path": "/custom-look-and-feel/reasoning-messages"
+      "shell_docs_path": "/custom-look-and-feel/reasoning-messages",
+      "deprecated": true
     },
     {
       "id": "reasoning-default-render",
@@ -263,7 +266,8 @@
       "description": "Built-in CopilotChatReasoningMessage renders without a custom slot",
       "kind": "testing",
       "shell_docs_path": "/custom-look-and-feel/reasoning-messages",
-      "og_docs_url": "https://docs.copilotkit.ai/custom-look-and-feel/reasoning-messages"
+      "og_docs_url": "https://docs.copilotkit.ai/custom-look-and-feel/reasoning-messages",
+      "deprecated": true
     },
     {
       "id": "reasoning-default",