Release v19.59.6

Fixed

• The ASP.NET Core readiness health check (chronicle, tagged ready) reports healthy only once the client is connected and artifact registration for the configured event store has succeeded, so a readiness probe no longer routes traffic before reactors, projections and constraints are registered. Until registration completes, or when it fails, the check reports its configured failure status and lists the failed artifacts. Apps that turn off AutoDiscoverAndRegister and do not run registration themselves stay healthy once connected. See health checks (#4872)