Fixtures feed 5xx falls back to cached

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": "Resilience — bracket still renders when the fixtures feed returns 5xx",
  "description": "When fixtures-feed.io is degraded (5xx response or timeout), the bracket page must still render the last-known-good fixtures from cache. Failing this means a single upstream blip during launch weekend takes the entire app down — unacceptable for a published prediction product.",
  "priority": "p0",
  "metadata": {
    "category": "resilience",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Open developer tools network panel and configure a request blocker that intercepts all requests to fixtures-feed.io and returns HTTP 503"
    },
    {
      "type": "action",
      "description": "Hard-reload the homepage so the fixtures feed is re-fetched under the simulated failure"
    },
    {
      "type": "assertion",
      "description": "Verify the bracket section still renders all 16 R16 fixture cards (served from a cached snapshot), with team names visible"
    },
    {
      "type": "assertion",
      "description": "Verify a small unobtrusive indicator (banner, badge, footnote) tells the user the predictions are from a cached snapshot, not live — phrasing like 'cached', 'last updated', or 'fixtures feed unavailable' is acceptable"
    }
  ]
}