/api/predict?team=XXX returns 404 for unknown team

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": "Predict API — unknown team returns 404 with an error shape",
  "description": "GET /api/predict?team=ZZZ for a team code that's not in the fixtures feed must return HTTP 404 with a documented error shape, not a 500 or an empty 200. Tests the error path that the bracket UI relies on to gracefully skip-or-show-fallback.",
  "priority": "p1",
  "metadata": {
    "category": "surfaces",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to /api/predict?team=ZZZ"
    },
    {
      "type": "assertion",
      "description": "Verify the response status code is 404, not 200 or 500"
    },
    {
      "type": "assertion",
      "description": "Verify the response body is a JSON object with an error field and a code field, with code equal to the string 'unknown_team'"
    }
  ]
}