Health

Is the app OK? Data feeds and code tests, one page — a red/yellow feed offers its own Re-run link

Data feeds

Loading status…
How to read this: "Data through" is the newest day actually present in each table — the honest check (a cron can "succeed" while writing nothing). 🟢 fresh and complete · 🟡 probably fine, worth a look (still running / known issue) · 🔴 data missing or stale. A 🟡/🔴 feed shows a Re-run → link that jumps straight to it on Refresh Data. Auto-refreshes every minute. Week / Month / Year show one row per day — the lights as they were saved each morning at ~4 AM Pacific, after the night's fetches finished.
Never miss a red: when a feed actually breaks (🔴) the system emails you and opens a tracked note in Open issues that stays there until someone closes it — so a problem can't quietly disappear before it's dealt with.

Latest run

Loading test results…

Recent runs

Loading…
How to read this: tests run automatically on every code change (GitHub Actions), and the results land here. 🟢 passed · 🔴 FAILED · 🟡 internal · ⚪ skipped.
🔴 FAILED means a person is needed — a page broken, data stale or wrong, security, money, or something you asked for that has been undone. Only these raise a red dot. 🟡 internal means the app works and it is our own housekeeping: a column a pixel too narrow, a layout at an unusual window size, a generated file gone stale. Internal failures still stop the change from going live, so they do get fixed — they just never interrupt you. (Before 31 Aug 2026 everything in the first two families was painted red, which is how “a button is one pixel narrow” sat here for five days wearing the same colour as a broken dashboard.)
Unit = one piece of logic checked on its own · Integration = the live data is correct & fresh · Smoke = a real page loads without breaking. Unit & smoke failures block a change from going live whatever their colour; integration checks watch live services, so an outage elsewhere can fail several at once — they are shown for awareness and never block or email.