[samcm]

The network overview has been stuck on its skeleton in production since the goodbye tables got bounds. Their data starts at 2026-11-11 06:57, after the last complete day, so chunksFor listed no days and sent day_start_date_in_values=''. The generated client's zod validator rejects that before sending, and with the app-wide retry: Infinity the read never settled, so census.isLoading held the whole page.

• chunksFor returns no chunks when there is no complete day (regression test fails on master, passes here).
• useDailyByClient retries a failed chunk 3 times and never retries a request the client rejected, so a broken table settles as empty instead of blocking every section.

Checked: pnpm lint, tsc, pnpm test:unit (926 passed), and a production build served with BACKEND=production: every section renders on mainnet at 1280 and 390 px, the Goodbyes section shows its empty state, no app console errors.

[redpandabot]

The change stops chunksFor from emitting a chunk with an empty day_start_date_in_values when a table's data begins after the last complete UTC day, and gives useDailyByClient's chunk queries a bounded retry policy that skips deterministic zod rejections. The guard mirrors the day-listing loop's own boundary exactly, is covered by regression tests, and the $ZodError check matches the error class actually thrown by the generated zod/mini request validators, so I found nothing that needs fixing.

---

_{Reviewed 3 changed file(s) @ 3748316c — no blocking issues found.
"Good enough is good enough."}