{
  "test_focus": "all",
  "data_status": "valid",
  "invalid_reason": "Unknown Invalid Data",
  "test_parameters": "focus=all, status=valid",
  "test_data": "country=CANADA, product=IPHONE 13 PRO, expected_message=YOUR ORDER HAS BEEN SUCCESSFULLY COMPLETED., last_name=yoon, password=Test123!, rowNum=1, first_name=garam, email=garam@gmail.com",
  "expected": "YOUR ORDER HAS BEEN SUCCESSFULLY COMPLETED.",
  "actual": "THANKYOU FOR THE ORDER.",
  "browser": "chrome",
  "os": "linux",
  "screenshot_url": "",
  "assertion_gap": "Expected 'YOUR ORDER HAS BEEN SUCCESSFULLY COMPLETED.' but got 'THANKYOU FOR THE ORDER.'",
  "is_ui_issue": false,
  "failure_type": "Logic Assertion",
  "ai_bucket": "needs_review",
  "summary": "Checkout success message text mismatch",
  "root_cause": "{\n  \"summary\": \"Checkout success message text mismatch\",\n  \"why_needs_review\": \"The failure shows a text mismatch between expected and actual checkout success messages. Both messages convey successful order completion but use different wording ('YOUR ORDER HAS BEEN SUCCESSFULLY COMPLETED.' vs 'THANK",
  "confidence": 75,
  "bug_description": "",
  "flaky_description": "",
  "needs_review_description": "",
  "impact": "",
  "root_cause_candidates": [],
  "log_line_references": [],
  "root_cause_analysis_jira": "_(No hypothesis scored above 90% — see full AI report and analysis JSON.)_",
  "recommendations": [
    "See AI analysis for details"
  ],
  "evidence": "\"evidence_needed\": [\n    \"Product owner confirmation on whether the success message text was intentionally changed\",\n    \"Check if there are feature flags or A/B tests affecting checkout success messaging\",",
  "claude_ok": true,
  "error_detail": null,
  "run_id": "run-1776036437946",
  "test_id": "testCases.CheckOut#verifyCheckOutSuccess[VALID-ALL]",
  "failure_index": 0,
  "failures_in_bundle": 2,
  "artifact_file_stem": "needs-review-run-1776036437946-01",
  "canonical_ai_id": "needs-review-run-1776036437946-01",
  "triage_classification_summary": {
    "BUG": 1,
    "FLAKY": 0,
    "NEEDS_REVIEW": 1
  },
  "triage_latest_run_id": "run-1776036437946",
  "ai_analysis_excerpt": "{\n  \"summary\": \"Checkout success message text mismatch\",\n  \"why_needs_review\": \"The failure shows a text mismatch between expected and actual checkout success messages. Both messages convey successful order completion but use different wording ('YOUR ORDER HAS BEEN SUCCESSFULLY COMPLETED.' vs 'THANKYOU FOR THE ORDER.'). This could be either a legitimate product change (BUG if test needs updating) or an A/B test/feature flag scenario (potentially FLAKY if inconsistent). The semantic similarity of the messages makes it unclear whether this is an intentional change or a test synchronization issue.\",\n  \"evidence_needed\": [\n    \"Product owner confirmation on whether the success message text was intentionally changed\",\n    \"Check if there are feature flags or A/B tests affecting checkout success messaging\",\n    \"Review recent deployments or commits that might have modified checkout confirmation text\",\n    \"Historical test results to see if this message has been consistent or varies between runs\",\n    \"Verify if multiple valid success messages are acceptable in the current product specification\"\n  ],\n  \"log_line_references\": [],\n  \"recommended_action\": \"Contact product team to verify the expected checkout success message text and whether 'THANKYOU FOR THE ORDER.' is a valid alternative to 'YOUR ORDER HAS BEEN SUCCESSFULLY COMPLETED.' Update test assertions if this is an intentional change.\"\n}",
  "artifacts": {
    "ai_bucket": "needs_review",
    "canonical_ai_id": "needs-review-run-1776036437946-01",
    "html_report": "reports/AI/needs_review/report/needs-review-run-1776036437946-01_ai_report.html",
    "analysis_json": "reports/AI/needs_review/analysis/needs-review-run-1776036437946-01_ai_rca.json",
    "summary_json": "reports/AI/needs_review/summary/needs-review-run-1776036437946-01_ai_summary.json"
  }
}