Readiness AND liveness ( §6.1 pinned the probe onto this path).

Two reasons to say no, and they are different failures:

• _READY unset — the instance is still warming.'s original meaning; the STARTUP probe waits on it.
• a stall the watchdog has been measuring for longer than LAWDB_STALL_READY_SECONDS (60 s) — the instance warmed fine and has since stopped answering.; the LIVENESS probe acts on it.

Deliberately still a pure in-memory read: no select 1, no pool checkout. That is what makes it safe as a liveness target ( §6.1) — a slow database must not turn this probe into a fleet-wide restart loop, which is exactly what /health would do.