Files
copilotkit__copilotkit/showcase/aimock/d6/langgraph-fastapi/headless-complete.json
Lukas Moschitz 797d30ca63 fix(showcase): port langgraph-fastapi gen-ui-headless-complete to parity
Two compounding defects kept this cell red:

1. Backend missing get_revenue_chart. headless_complete.py never registered
   the revenue-chart tool, so the chart-turn never emitted a tool call and the
   card never mounted. Port LGP's get_revenue_chart tool + its system-prompt
   routing rule (tool return shape byte-identical to LGP).

2. Stale turnIndex fixtures caused turn-2 and turn-4 loops to the recursion
   limit. Align to LGP's canonical shape:
   - tool-rendering.json (shared): AAPL first-leg turnIndex:0 -> hasToolResult:false
     so it stops re-firing at turnIndex>=2 in the multi-pill thread.
   - headless-complete.json: rewrite to LGP's structure (narration/toolCallId
     fixtures first, tool-call legs after with userMessage+context only, no
     stale turnIndex); drop the divergent fastapi-only highlight fixtures,
     subsumed by the broader substring fixture.

D6 langgraph-fastapi:gen-ui-headless-complete now green (two real ~29s runs);
tool-rendering re-verified green (shared-fixture no regression).
2026-07-24 16:39:55 +02:00

137 lines
6.6 KiB
JSON

{
"_meta": {
"description": "D6 fixtures for langgraph-fastapi / headless-complete",
"sourceFile": "d5-all.json",
"copiedFrom": "langgraph-python",
"created": "2026-05-21",
"_note": "Narration fixtures (toolCallId) listed FIRST so they win when last message is a matching tool result. Toolcall fixtures listed AFTER and use only userMessage+context so they match on the initial user turn regardless of prior assistant/tool history. Mirrors the green langgraph-python headless-complete.json byte-for-byte (context swapped) — the prior fastapi copy had diverged, keeping stale turnIndex:0 gates on the revenue/highlight toolcall fixtures that re-fired under relaxed turnIndex matching in the 4-pill gen-ui-headless-complete thread and looped the graph to its recursion limit."
},
"fixtures": [
{
"_comment": "headless-complete weather pill narration — matches when the get_weather tool result with id call_d5_headless_weather_001 is the last message. The 'tokyo' textToken assertion is satisfied by the city name. Narration verbatim matches the headless-complete.spec.ts assertion `toContainText('Tokyo is 22°C and partly cloudy.')`.",
"match": {
"toolCallId": "call_d5_headless_weather_001",
"context": "langgraph-fastapi"
},
"response": {
"content": "Tokyo is 22°C and partly cloudy. The headless WeatherCard above shows the sunny snapshot from the tool."
}
},
{
"_comment": "headless-complete stock pill narration — matches when the get_stock_price tool result with id call_d5_headless_stock_001 is the last message. textToken 'aapl' satisfied by ticker mention.",
"match": {
"toolCallId": "call_d5_headless_stock_001",
"context": "langgraph-fastapi"
},
"response": {
"content": "AAPL is at $189.42, up 1.27% on the day."
}
},
{
"_comment": "headless-complete highlight pill narration — matches when the highlight_note tool result with id call_d5_headless_highlight_001 is the last message.",
"match": {
"toolCallId": "call_d5_headless_highlight_001",
"context": "langgraph-fastapi"
},
"response": {
"content": "Highlighted 'ship the demo on Friday' for you above."
}
},
{
"_comment": "headless-complete revenue chart narration — matches when the get_revenue_chart tool result with id call_d5_headless_revenue_chart_001 is the last message.",
"match": {
"toolCallId": "call_d5_headless_revenue_chart_001",
"context": "langgraph-fastapi"
},
"response": {
"content": "Here is the chart of revenue over the last six months — quarterly revenue grew steadily, peaking in June."
}
},
{
"_comment": "headless-complete weather pill toolcall — emit get_weather for Tokyo. Probe sends \"What's the weather in Tokyo?\". Narrowed to the full phrase 'What's the weather in Tokyo' so this no longer shadows the D6 tool-rendering 'Chain tools' pill (whose prompt contains 'weather in Tokyo' as a substring) — that pill needs to hit its own 3-tool emission fixture in tool-rendering.json. Only userMessage+context discriminators because narration fixtures above (toolCallId) already win once the tool result lands.",
"match": {
"userMessage": "What's the weather in Tokyo",
"context": "langgraph-fastapi"
},
"response": {
"toolCalls": [
{
"id": "call_d5_headless_weather_001",
"name": "get_weather",
"arguments": "{\"location\":\"Tokyo\"}"
}
]
}
},
{
"_comment": "headless-complete stock pill toolcall — emit get_stock_price for AAPL. Probe sends \"What's the price of AAPL right now?\". Narrowed to 'price of AAPL right now' so this no longer shadows the D6 tool-rendering 'Stock price' pill which sends \"What's the current price of AAPL?\" (also containing 'price of AAPL' as a substring) — that pill needs its own deterministic-price fixture in tool-rendering.json.",
"match": {
"userMessage": "price of AAPL right now",
"context": "langgraph-fastapi"
},
"response": {
"toolCalls": [
{
"id": "call_d5_headless_stock_001",
"name": "get_stock_price",
"arguments": "{\"ticker\":\"AAPL\"}"
}
]
}
},
{
"_comment": "headless-complete highlight pill toolcall — emit highlight_note. Probe sends \"Highlight this note for me: 'ship the demo on Friday'.\" so userMessage substring 'ship the demo on Friday' catches it.",
"match": {
"userMessage": "ship the demo on Friday",
"context": "langgraph-fastapi"
},
"response": {
"toolCalls": [
{
"id": "call_d5_headless_highlight_001",
"name": "highlight_note",
"arguments": "{\"text\":\"ship the demo on Friday\",\"color\":\"yellow\"}"
}
]
}
},
{
"_comment": "headless-complete revenue chart toolcall — emit get_revenue_chart (no args). Probe sends 'Show me a chart of revenue over the last six months.'. Includes a short leading `content` snippet so the word 'revenue' lands in the assistant bubble synchronously with the tool-call emission. Without this, the chart card's title falls back to 'Chart' during the `executing` render phase (result still undefined), and the conversation-runner's count-based settle can fire its 1500ms quiet window before the narration follow-up message arrives — leaving the assistant text without 'revenue' on the probe's first attempt.",
"match": {
"userMessage": "chart of revenue over the last six months",
"context": "langgraph-fastapi"
},
"response": {
"content": "Pulling the revenue chart for the last six months...",
"toolCalls": [
{
"id": "call_d5_headless_revenue_chart_001",
"name": "get_revenue_chart",
"arguments": "{}"
}
]
}
},
{
"match": {
"userMessage": "trigger the headless interrupt",
"turnIndex": 0,
"context": "langgraph-fastapi"
},
"response": {
"content": "Interrupt raised. The agent has paused at a graph-level interrupt and is waiting for user input. Reply with 'yes' or 'no' to resume."
}
},
{
"match": {
"userMessage": "resolve the interrupt with yes",
"turnIndex": 0,
"context": "langgraph-fastapi"
},
"response": {
"content": "Interrupt resolved with 'yes'. The agent resumed execution from the suspended node and produced its final answer."
}
}
]
}