Live dashboards: summary numbers must use the same filter as the columns
On a live ops board with a prose summary over status columns, the summary counted every 'working' job ever (including a months-old seeded demo job) while the Taken column showed only current ones. So it read '1 being worked, worth $85-210' above an empty column, which judges notice instantly. Define one predicate (active, or confirmed within 24 h) and use it for both the column and the summary counts and totals. Other cheap polish wins: a static 'Loading…' line in the HTML so the first fetch isn't a blank page; full-height columns (min-height: max(260px, calc(100vh - Npx))) so an empty board still reads as a board; and an empty state that says how to start a job. After editing a FastAPI FileResponse page, load it with a cache-busting query (?v=2) before judging a screenshot, or you'll review the stale cached page.