mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
c414fbad23
Refresh d6 fixtures across the rollout cohort: ag2, built-in-agent,
claude-sdk-{python,typescript}, crewai-crews, google-adk, langgraph-fastapi,
langgraph-typescript, langroid, llamaindex, mastra, ms-agent-{dotnet,python},
pydantic-ai, strands. Companion d4/{langgraph-typescript,mastra,ms-agent-dotnet}
chat.json refreshes. Add the missing ms-agent-python/gen-ui-custom.json
to bring the integration up to the standard pill set.
Also narrow aimock/shared/common.json's generic 'hello' fixture to
'hello world' so it no longer shadows D6 pills whose prompts contain
'hello' as a substring (e.g. langgraph-python headless-simple sends
'Say hello in one short sentence.'). 'hello world' is unused by any
current demo pill, so the fixture remains a manual-typing fallback
without poisoning fixture matching.
This is a mid-rollout snapshot — fixture coverage is uneven across
integrations and rides alongside the conveyance shims landed earlier
in this branch.
136 lines
5.4 KiB
JSON
136 lines
5.4 KiB
JSON
{
|
|
"_meta": {
|
|
"description": "D6 fixtures for ag2 / headless-complete",
|
|
"sourceFile": "d5-all.json",
|
|
"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."
|
|
},
|
|
"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.",
|
|
"match": {
|
|
"toolCallId": "call_d5_headless_weather_001",
|
|
"context": "ag2"
|
|
},
|
|
"response": {
|
|
"content": "Tokyo is sunny right now — about 68°F with light winds. Want a forecast?"
|
|
}
|
|
},
|
|
{
|
|
"_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": "ag2"
|
|
},
|
|
"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": "ag2"
|
|
},
|
|
"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": "ag2"
|
|
},
|
|
"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?'. Only userMessage+context discriminators because narration fixtures above (toolCallId) already win once the tool result lands.",
|
|
"match": {
|
|
"userMessage": "weather in Tokyo",
|
|
"context": "ag2"
|
|
},
|
|
"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?\".",
|
|
"match": {
|
|
"userMessage": "price of AAPL",
|
|
"context": "ag2"
|
|
},
|
|
"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": "ag2"
|
|
},
|
|
"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": "ag2"
|
|
},
|
|
"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": "ag2"
|
|
},
|
|
"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": "ag2"
|
|
},
|
|
"response": {
|
|
"content": "Interrupt resolved with 'yes'. The agent resumed execution from the suspended node and produced its final answer."
|
|
}
|
|
}
|
|
]
|
|
}
|