Files
copilotkit__copilotkit/showcase/aimock/d6/ms-agent-python/frontend-tools-async.json
Ran Shem Tov 02f079180d fix(showcase): MAF Python frontend-tools-async + gen-ui-open green; quarantine multimodal
- frontend-tools-async: drop the stray broad 'project planning' fixture entry that
  substring-shadowed 'Find my notes about project planning' -> run-loop. Green.
- gen-ui-open + gen-ui-open-advanced: remove 6 gen-ui-open-owned strays from
  gen-ui-tool-based.json ('3D axis visualization', 'Inline expression evaluator',
  'render an open gen-ui element', 'continue the advanced gen-ui flow') that
  collided (same context, different responses) with gen-ui-open.json. Green;
  gen-ui-tool-based unaffected.
- multimodal: quarantine. On main + latest deps the browser gets 200 from the
  runtime but never starts a run (runStartCount=0) — a shared multimodal
  frontend/runtime issue (identical frontend to langgraph; agent works via direct
  POST; my #5985 fix doesn't change it). Genuine gap, needs shared-layer work.

Full D6 now 36/36 green on official latest (ag-ui 1.0.1, core 1.13.0, openai 1.12.0).
2026-08-05 14:12:16 +03:00

111 lines
5.3 KiB
JSON

{
"_meta": {
"description": "D6 fixtures for ms-agent-python / frontend-tools-async",
"sourceFile": "d5-all.json",
"created": "2026-05-21",
"copiedFrom": "langgraph-python"
},
"fixtures": [
{
"match": {
"userMessage": "auth check turn 1",
"turnIndex": 0,
"context": "ms-agent-python"
},
"response": {
"content": "Authenticated session is active. The runtime accepted your request because the Authorization header carried the demo bearer token."
}
},
{
"match": {
"userMessage": "fetch the async metric",
"turnIndex": 0,
"context": "ms-agent-python"
},
"response": {
"content": "The async tool resolved with the requested metric. The frontend handler awaited completion before forwarding the result back to the agent \u2014 async-streaming behavior confirmed."
}
},
{
"_comment": "frontend-tools-async \u2014 project-planning pill, follow-up content keyed on the prior tool's id. Comes BEFORE the tool-emitting fixture so iteration 2 (after the async handler returns) hits this branch instead of re-emitting query_notes. hasToolResult gates were dropped because they broke after the user clicked another tool-using pill earlier in the same thread.",
"match": {
"userMessage": "Find my notes about project planning",
"toolCallId": "call_d5_query_notes_project_planning_001",
"context": "ms-agent-python"
},
"response": {
"content": "You have notes on project planning: \"Q2 project planning kickoff\" and \"Project planning retrospective notes\". Let me know if you want a summary of either."
}
},
{
"_comment": "frontend-tools-async \u2014 project-planning pill. 1st turn: query_notes tool call. Specific match wins over the broad 'plan' fixture in feature-parity.json (d5-all.json loads first). turnIndex gate dropped \u2014 the multi-pill sequential e2e (frontend-tools-async.spec.ts:149) clicks earlier pills first, leaving prior tool/assistant turns in the thread, so this user message is no longer at turnIndex 0. The toolCallId-keyed follow-up fixture above still wins for iteration 2 (last message is tool with that id); this fixture only fires when last-message.role=user.",
"match": {
"userMessage": "Find my notes about project planning",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_query_notes_project_planning_001",
"name": "query_notes",
"arguments": "{\"keyword\":\"project planning\"}"
}
]
}
},
{
"_comment": "frontend-tools-async \u2014 auth pill, follow-up content keyed on the prior tool's id. Must come BEFORE the tool-emitting fixture.",
"match": {
"userMessage": "Search my notes for anything related to auth",
"toolCallId": "call_d5_query_notes_auth_001",
"context": "ms-agent-python"
},
"response": {
"content": "You have one note related to auth: \"Planning: migrate auth to passkeys\" \u2014 it covers WebAuthn library options and a fallback for unsupported browsers."
}
},
{
"_comment": "frontend-tools-async \u2014 auth pill. 1st turn: query_notes tool call. Beats the showcase-assistant catch-all in feature-parity.json by virtue of d5-all.json's load order and a longer specific substring match. turnIndex gate dropped \u2014 multi-pill sequential e2e leaves prior turns in the thread before this pill is clicked, so the prompt is no longer at turnIndex 0. The toolCallId-keyed follow-up above still wins for iteration 2.",
"match": {
"userMessage": "Search my notes for anything related to auth",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_query_notes_auth_001",
"name": "query_notes",
"arguments": "{\"keyword\":\"auth\"}"
}
]
}
},
{
"_comment": "frontend-tools-async \u2014 reading pill, follow-up content keyed on the prior tool's id. Must come BEFORE the tool-emitting fixture. Locked narration leading phrase per spec test #4 assertion.",
"match": {
"userMessage": "Do I have any notes tagged reading",
"toolCallId": "call_d5_query_notes_reading_001",
"context": "ms-agent-python"
},
"response": {
"content": "You have a note titled \"Book recommendations\" that is tagged with \"reading.\" It includes the following books: Thinking Fast and Slow by Daniel Kahneman, The Design of Everyday Things by Don Norman."
}
},
{
"_comment": "frontend-tools-async \u2014 reading pill. 1st turn: query_notes tool call. turnIndex gate dropped \u2014 multi-pill sequential e2e leaves prior turns in the thread before this pill is clicked, so the prompt is no longer at turnIndex 0. The toolCallId-keyed follow-up above still wins for iteration 2.",
"match": {
"userMessage": "Do I have any notes tagged reading",
"context": "ms-agent-python"
},
"response": {
"toolCalls": [
{
"id": "call_d5_query_notes_reading_001",
"name": "query_notes",
"arguments": "{\"keyword\":\"reading\"}"
}
]
}
}
]
}