Release v16.1.1

Summary

The Chronicle server always serves its port over TLS. This aligns the .NET client with that reality — certificate validation is now on by default and the obsolete plaintext option is removed — and adds a dedicated health endpoint port for orchestrator and load-balancer probes.

Added

• Optional dedicated health endpoint port (Cratis:Chronicle:Health:Port) that publishes the health endpoint on its own HTTP/1.1 port, with TLS optionally disabled (Health:Tls) for orchestrator and load-balancer probes that cannot validate a self-signed certificate. When unset, the health endpoint stays on the main port.
• skipTlsValidation connection-string option (and SkipCertificateValidation on the client TLS options) to connect over TLS without validating the server certificate — for a trusted server on a trusted network. The built-in development connection string enables it so development works against the server's self-signed certificate.

Changed

• The .NET client now validates the server certificate by default. A self-signed or otherwise untrusted certificate is rejected unless validation is skipped or a matching client certificate is configured.

Removed

• The client disableTls connection-string option and the WithTlsDisabled/WithTlsEnabled builder methods. The server always serves TLS, so a plaintext client connection no longer connects to anything.

Security

• The client no longer implicitly accepts self-signed or name-mismatched server certificates in production; validation must be skipped explicitly via skipTlsValidation.

Note: Removing disableTls and validating certificates by default are breaking changes for clients that relied on the previous behavior — set skipTlsValidation=true (or configure a valid certificate) to migrate. Labeled patch at the maintainer's request.