agent-qa Result Triage

Workflow

1. Start with agent_qa_get_run_digest for the run's verdicts, its post-processing chain, the outcome of its steps, the changes its marks applied, and the counts. This is the triage read over this surface.
2. Fetch the rest of the evidence before deciding:
   • agent_qa_get_run_overview, every test and step with its verdict, and the address of each screenshot, evidence document and served record the run recorded.
   • agent_qa_get_run_evidence, only the pieces the failure needs, by the overview's addresses: a step's console, network, a11y, aria or variables document ("action": "runs.evidence"), or a screenshot by its sha ("action": "runs.artifact"), which comes back as an image.
   • agent_qa_get_entity on the run reference, for the run's own card and its suite context.
   • agent_qa_list_runs, to see whether related runs failed the same way.
3. Use the digest's verdict as the default classification unless stronger evidence contradicts it. It is a reading a job produced, not a verdict handed down.
4. Compare recent related runs when the evidence you have makes the comparison meaningful.
5. Return a concise triage result: category, confidence, evidence, likely fix area, and next action.
6. For code changes, switch to agent-qa-debug-fix after triage is complete.

Categories

Use one of the fixed categories from references/triage-categories.md:

• timeout
• appium_startup
• browser_disconnect
• element_not_found
• assertion_failure
• hook_failure
• infrastructure
• unknown_failure

Evidence Rules