agent-qa-result-triagelisted

# Agent QA Result Triage ## Overview Classify a failed Agent QA run from its recorded evidence instead of guessing. Inspect the run, steps, artifacts, and logs; choose one fixed category; and return confidence, likely ownership, and the next evidence-backed action. ## When to Use - Investigating a failed or interrupted Agent QA run. - Inspecting run artifacts, step results, or execution logs. - Comparing recent related runs for recurring failure patterns. - Deciding whether a failure belongs to a test, product, hook, browser/mobile runtime, or infrastructure owner. ## Workflow 1. Start with `agent_qa_get_run` for run status, suite child context, steps, and attempts. 2. Fetch evidence before deciding: - `agent_qa_get_run_artifact` - `agent_qa_get_run_steps` - `agent_qa_get_run_logs` - `agent_qa_get_run_execution_logs` 3. Call `agent_qa_classify_failure` and use its category as the default classification unless stronger evidence contradicts it. 4. Compare recent related runs when they are available in the classifier output. 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 exactly one category from `references/triage-categories.md`: - `timeout` - `appium_startup` - `browser_disconnect` - `element_not_found` - `assertion_failure` - `hook_failure` - `infrastructure` - `unknown_failure` ## Evidence Rules - Quote o