v0.4.2

New features

• A new data-olympus verify command checks that a running knowledge-base
  server is healthy and answering correctly. It runs liveness, readiness, a
  search round-trip, and an enforcement check against a target you name, prints a
  clear pass/fail summary (or JSON), and returns a distinct exit code when the
  server is unreachable versus when a check fails. Handy in scripts and as a
  release or deployment smoke test.
• Behind the scenes, the project gained a staged-promotion release pipeline: a
  release candidate is built, verified on a live instance, and then promoted as
  the exact same image, so what ships is exactly what was tested. This is
  internal tooling and does not change how you run the server.
• Registry listing polish: a Glama score badge and clearer MCP tool metadata so
  catalog sites can describe the server more accurately.

Fixed

• Clarified, for anyone running the server behind a reverse proxy or ingress,
  that the public hostname must be added to FASTMCP_HTTP_ALLOWED_HOSTS. Without
  it, health probes pass while real requests are refused with a 421. See
  docs/serving.md and docs/operations.md section 3.4.