TudorandClaude Opus 5.5
59ea8a4bdd
PR Checks / Frontend Typecheck + Tests (pull_request) Successful in 1m12s
PR Checks / Backend Smoke (pull_request) Successful in 9s
PR Checks / Build Backend (no push) (pull_request) Successful in 18s
PR Checks / Build Frontend (no push) (pull_request) Successful in 1m18s
PR Checks / Build Pipeline (no push) (pull_request) Successful in 11s
PR Checks / AI Code Review (Claude) (pull_request) Successful in 18s
The search page fetched LA averages with cache: 'force-cache', which serves any stored response, however old, without asking the server. One failed request (a staging deploy restart; the July proxy outage) was stored and replayed on every later visit, and the error was swallowed, so the "vs LA avg" delta silently vanished from every secondary row in that browser. A Playwright profile still held a 500 dated 5 July. The default cache mode honours the API's Cache-Control (five minutes), so a good answer is still reused and an error never is. Browsers holding a stored failure recover on their next visit. A journey now checks that a mainstream secondary's row shows the comparison: nothing did, which is how it could go missing unnoticed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>