Health endpoint: service.no_health_endpoint

Low. A backend service that nothing can ask "are you working?". Without a health endpoint, a load balancer or uptime monitor cannot tell a crashed service from a slow one, and a deploy cannot check that the new version started.

The check looks at backend services only. It is not applicable to an app with no backend, such as a static frontend talking to Supabase. It reports could not assess when a service's routes cannot be determined, for example when a router prefix is read from settings, because "no health route found" is not the same as "no health route".

Fix: add a route such as /health that returns 200 without touching the database, and point your platform's health check at it.