Empty state tests

Empty-state QC verifies that every list, grid, rail, sidebar block, and search result renders a documented empty state when the data is missing — not a blank rectangle, not a 0-height collapse, not a generic "No data". Empty states are usually the first thing skipped during build and the first thing users encounter when the dataset is small.

Empty-state contract

• Every list / grid / rail with potentially-zero records has an empty state spec in its module documentation. No empty state = no merge.
• The empty state explains why the list is empty in the active locale + what the user can do next (CTA or link to a broader view).
• When filters caused the empty state, the state quotes the active filters back ("No events match Egypt + demo-day + this week") with a CTA to clear filters.
• When the empty state is structural (e.g. a brand-new founder profile with no startups yet), it shows the documented illustration + reads as a normal pre-content state, not as an error.
• Empty states have RTL parity — illustrations and CTAs mirror under /ar/*.