agent-qa Debug Fix

Workflow

1. Start with evidence collection:
   • agent_qa_get_run_digest, the run's verdicts, its post-processing chain, the outcome of its steps, and what it produced. This is the triage read over this surface.
   • agent_qa_get_entity on the run reference, the run's own card.
   • 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 what 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_list_runs, recent runs, when the question is whether this failure is new.
2. Treat the digest's verdict as a hypothesis, not a conclusion, it is the reading a job produced, and the evidence it points at is what settles the question.
3. Identify the failing surface: test definition, hook, application under test, runtime infrastructure, or agent behavior.
4. Inspect the relevant application source, tests, suites and hooks directly. Do not infer patches from evidence alone.
5. Apply the smallest code or YAML change that explains the evidence.
6. Re-run the narrowest affected agent-qa test, suite, hook, or unit test. Name the test files to agent_qa_start_run with patterns (paths or globs).
7. Report the root cause, changed files, verification command, and any remaining risk.

Fix Rules