wehub-resource-sync
116 lines
6.1 KiB
JSON
116 lines
6.1 KiB
JSON
{
|
|
"_meta": {
|
|
"description": "D6 fixtures for langgraph-python / gen-ui-headless-complete",
|
|
"sourceFile": "headless-complete.json",
|
|
"copiedFrom": "langgraph-python",
|
|
"_note": "Alias of the headless-complete demo's 4 gen-UI pills (weather/stock/highlight/revenue) for the gen-ui-headless-complete probe (showcase/harness/src/probes/scripts/d5-gen-ui-headless-complete.ts -> fixtureFile 'gen-ui-headless-complete.json'), which had no matching fixture in any slug so its first leg 503'd under strict. Narration (toolCallId) fixtures FIRST so they win when the last message is a matching tool result; toolcall (userMessage+context) fixtures AFTER with NO turnIndex gate so each of the 4 sequential pill turns in one chat thread matches regardless of prior assistant/tool history (the turnIndex multi-turn match-gate bug). Modeled on the green langgraph-python pattern. Interrupt fixtures intentionally omitted (interrupt-headless is a separate cluster item)."
|
|
},
|
|
"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-python"
|
|
},
|
|
"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-python"
|
|
},
|
|
"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-python"
|
|
},
|
|
"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-python"
|
|
},
|
|
"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-python"
|
|
},
|
|
"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-python"
|
|
},
|
|
"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-python"
|
|
},
|
|
"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-python"
|
|
},
|
|
"response": {
|
|
"content": "Pulling the revenue chart for the last six months...",
|
|
"toolCalls": [
|
|
{
|
|
"id": "call_d5_headless_revenue_chart_001",
|
|
"name": "get_revenue_chart",
|
|
"arguments": "{}"
|
|
}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
}
|