404 page for unknown route

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": "Unknown route returns a real 404 (not the bracket page)",
  "description": "Routes that don't map to a defined page must return HTTP 404 with a recognisable not-found body, NOT silently fall back to rendering the bracket index. Catches the common static-export mis-config where Amplify SPA rewrites mask 404s as 200s and break crawlers.",
  "priority": "p1",
  "metadata": {
    "category": "surfaces",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to /this-route-does-not-exist-xyz"
    },
    {
      "type": "assertion",
      "description": "Verify the page does NOT show the R16 bracket fixture grid (no list of 16 match cards visible)"
    },
    {
      "type": "assertion",
      "description": "Verify the page shows a recognisable not-found indicator — either the text '404' visible, or a heading containing the word 'not found' (case insensitive), or both"
    },
    {
      "type": "assertion",
      "description": "Verify a link or button is visible that returns the user to the bracket homepage"
    }
  ]
}