agent-qa Debug Fix

Workflow

1. Start with evidence collection:

• agent_qa_get_run
• agent_qa_get_run_steps
• agent_qa_get_run_artifact
• agent_qa_get_run_logs
• agent_qa_get_run_execution_logs

1. Call agent_qa_classify_failure and treat its category as a hypothesis, not a verdict.
2. Identify the failing surface: test definition, hook, application under test, runtime infrastructure, or agent behavior.
3. Inspect the relevant local files directly. Do not infer patches from artifacts alone.
4. Apply the smallest code or YAML change that explains the evidence.
5. Re-run the narrowest affected agent-qa test, suite, hook, or unit test.
6. Report the root cause, changed files, verification command, and any remaining risk.

Fix Rules

• Do not invent selectors, screen states, screenshots, logs, or source files.
• Do not rewrite a test just to make it pass if the artifact shows a product or runtime defect.
• Preserve canonical agent-qa IDs when editing tests, suites, hooks, or memory files.
• Prefer agent_qa_validate_test, agent_qa_validate_suite, and agent_qa_validate_definition before re-running edited YAML.
• When MCP is unavailable, use dashboard REST APIs or local .agent-qa artifacts and state that MCP evidence was unavailable.