/match/[id] permalink renders fixture detail

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": "Match detail page — per-fixture permalink renders correctly",
  "description": "GET /match/r16-1 returns a per-fixture detail page with both team names, the agent's predicted scoreline, the agent's reasoning text, and a back-to-bracket link. The page is fully rendered (no client-only blank-shell pattern that breaks for crawlers + share previews).",
  "priority": "p0",
  "metadata": {
    "category": "surfaces",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to /match/r16-1"
    },
    {
      "type": "assertion",
      "description": "Verify the page heading or main title clearly identifies the two teams in the R16-1 match — Brazil and Croatia — both names present and visible"
    },
    {
      "type": "assertion",
      "description": "Verify the page shows the agent's predicted scoreline for this match in a prominent area (not buried in a tooltip)"
    },
    {
      "type": "assertion",
      "description": "Verify the page contains a reasoning paragraph of at least 20 characters explaining the prediction"
    },
    {
      "type": "assertion",
      "description": "Verify a back-to-bracket link or button is visible that navigates to / when clicked"
    }
  ]
}