Index renders the R16 bracket

What TestSprite reads

The testing agent reads this JSON, opens the deployed URL in headless Chromium, executes each action step, evaluates each assertion. Verdict: passed / failed / blocked / inconclusive.

{
  "projectId": "1ad26753-ee03-4689-8f0f-6fa5d67c5c72",
  "type": "frontend",
  "name": "Index — renders all 16 R16 fixtures in a bracket layout",
  "description": "GET / returns the bracket page. The page must display all 16 R16 fixtures (each with home team, away team, and the agent's predicted scoreline) laid out as a visible bracket. Tests page presence + layout + content cardinality, not specific prediction values (each agent predicts differently).",
  "priority": "p0",
  "metadata": {
    "category": "surfaces",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to the homepage"
    },
    {
      "type": "assertion",
      "description": "Verify the page renders a bracket section containing exactly 16 distinct match fixture cards (one per R16 match), each showing two team names and a predicted scoreline like 'N-M'"
    },
    {
      "type": "assertion",
      "description": "Verify the team codes Brazil, Argentina, France, England, Germany, Spain, Croatia, Portugal appear somewhere within the bracket section (each as part of a fixture, not in a header)"
    },
    {
      "type": "assertion",
      "description": "Verify the bracket section visually groups fixtures into distinct R16 / QF / SF / Final stages (e.g. via column headings or separators that name those stages)"
    }
  ]
}