forked from CopilotKit/CopilotKit
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathheadless-complete.json
More file actions
136 lines (136 loc) · 6.31 KB
/
Copy pathheadless-complete.json
File metadata and controls
136 lines (136 loc) · 6.31 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
{
"_meta": {
"description": "D6 fixtures for ms-agent-python / 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.",
"copiedFrom": "langgraph-python"
},
"fixtures": [
{
"_comment": "headless-complete weather pill narration \u2014 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\u00b0C and partly cloudy.')`.",
"match": {
"toolCallId": "call_d5_headless_weather_001",
"context": "ms-agent-python"
},
"response": {
"content": "Tokyo is 22\u00b0C and partly cloudy. The headless WeatherCard above shows the sunny snapshot from the tool."
}
},
{
"_comment": "headless-complete stock pill narration \u2014 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": "ms-agent-python"
},
"response": {
"content": "AAPL is at $189.42, up 1.27% on the day."
}
},
{
"_comment": "headless-complete highlight pill narration \u2014 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": "ms-agent-python"
},
"response": {
"content": "Highlighted 'ship the demo on Friday' for you above."
}
},
{
"_comment": "headless-complete revenue chart narration \u2014 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": "ms-agent-python"
},
"response": {
"content": "Here is the chart of revenue over the last six months \u2014 quarterly revenue grew steadily, peaking in June."
}
},
{
"_comment": "headless-complete weather pill toolcall \u2014 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) \u2014 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": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_headless_weather_001",
"name": "get_weather",
"arguments": "{\"location\":\"Tokyo\"}"
}
]
}
},
{
"_comment": "headless-complete stock pill toolcall \u2014 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) \u2014 that pill needs its own deterministic-price fixture in tool-rendering.json.",
"match": {
"userMessage": "price of AAPL right now",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_headless_stock_001",
"name": "get_stock_price",
"arguments": "{\"ticker\":\"AAPL\"}"
}
]
}
},
{
"_comment": "headless-complete highlight pill toolcall \u2014 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": "ms-agent-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 \u2014 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 \u2014 leaving the assistant text without 'revenue' on the probe's first attempt.",
"match": {
"userMessage": "chart of revenue over the last six months",
"context": "ms-agent-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": "{}"
}
]
}
},
{
"match": {
"userMessage": "trigger the headless interrupt",
"turnIndex": 0,
"context": "ms-agent-python"
},
"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": "ms-agent-python"
},
"response": {
"content": "Interrupt resolved with 'yes'. The agent resumed execution from the suspended node and produced its final answer."
}
}
]
}