Four weeks ago we shipped the 1.0.0 release candidate. Today it’s 1.0.8, and the arc between them was mostly one word: high availability. Clustering, auto-failover, etcd with TLS on by default, backup/restore that survives a schema change, per-node dashboards so you can see which member is doing what — a long parade of small, unglamorous fixes that add up to “this thing stays up.”

But shipping infrastructure people log into means asking them to trust it, and “trust me” isn’t a feature. So 1.0.8 also ships a receipt. Every release now runs the full suite on a dedicated runner before the images publish:

• 1792 passing, 0 failing — unit and service logic, full HTTP across every domain, real tac_plus-ng / FreeRADIUS / NAC daemons doing live auth, and sustained-rate load through an HA failover.
• 70% backend line coverage, commit-pinned, dated.
• Three known-gap cases tracked openly as expected-fail — not swept under the rug, not counted as green.

That last line matters more than the big number. Anyone can quote a test count; we’d rather tell you exactly which cases we haven’t nailed yet. The full breakdown ships in the tarball as TESTING.md — a plain table you can read before you ever pull an image.

Self-hosted, artifact-only, Elastic License 2.0. Same as always: kick the tyres, file issues, tell us what’s rough.