v0.55.1

Fixed

• Deployment docs now name the HTTP bind keys Flair reads instead of the ignored http.host. (#1760)

  Heads-up: http.host is not read and is now documented as such. An
  install that was only wide because the default before 0.55.0 bound every
  interface narrows to 127.0.0.1 on the next flair restart or
  flair upgrade. Set httpBind: (or --http-bind / FLAIR_HTTP_BIND) to
  keep the HTTP listener reachable.

• The Metal-default doctor finding is an advisory warning, not a blocking error. (#1761)

  Heads-up: on a darwin-arm64 host that never set
  FLAIR_EMBED_GPU_LAYERS, the derived Metal default now shows a persistent
  warning instead of failing flair doctor. Set the variable explicitly if
  you want an unconfirmed offload to remain a loud, blocking error.

• flair upgrade now finds a systemd unit that names the tree through a symlinked path. (#1758)

  Heads-up: if your systemd install's unit names the tree through a
  symlinked path, an upgrade before this release may have restarted the
  instance outside the unit — systemctl status no longer describes the
  running process and systemd supervision is lost. This release fixes
  discovery for future upgrades; it does not re-adopt an already-unmanaged
  process, and Flair has no systemd equivalent of its launchd detach check, so
  nothing in the product will tell you. Run systemctl restart <unit> to bring
  it back under supervision, or set FLAIR_SYSTEMD_UNIT=<unit> if discovery
  still does not find it. The loose matching shipped in v0.54.2 as well, so an
  install never upgraded past 0.54.2 can be affected too.

---

Full record: CHANGELOG.md