/gauntlet: default expanded-view sort to date, bust stale cache
Two UX issues surfaced: 1. The expanded comparison table (click any signal row) sorted rows by
Two UX issues surfaced:
- The expanded comparison table (click any signal row) sorted rows by
"where this signal beats the most contenders" (sortScore). Readers expected the top row to be the most recent bet, so a user spotting a March 20 Genoa v Udinese on top of an April 11 Atalanta v Juventus at the bottom thought the list was wrong or incomplete.
Now defaults to date-desc. Kept "wins" as a sort toggle (still useful for "where does this signal actually deliver"), added a filter/sort label bar showing row count, and prefixed each row with the MM-DD so the sort order is visible.
- /api/gauntlet had no cache-control headers, so a browser that loaded
the page before a fix landed would see yesterday's coverage numbers forever (we saw a stale 164/181 in the leaderboard while the fresh API returns 180/181). Added force-dynamic + revalidate = 0 + cache-control: no-store header, and switched the client fetches to cache: "no-store" so both ends refuse to cache.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>