Readiness Check

Readiness probe: 200 only when the component catalog is actually usable.

⚡ This endpoint is a BARRIER, not a poll. main.py preloads the catalog in a background task after the server starts serving, so there is a window where the port answers and no part can be found. get_database_stats() calls _ensure_loaded(), which blocks under a lock until that load finishes — so ONE request here waits out startup instead of sampling it. That is what makes it usable as a start-up gate for an automated run (frontend/playwright.config.ts waits on this URL).

⛔ Two distinct not-ready states, deliberately not collapsed: the call RAISED (service broken), or it returned an EMPTY catalog. The second is the one that used to report ready — see the comment in health_check above.