v0.1.7

Added

• Project website under site/ (Astro + Starlight): landing page plus
  user-facing docs — getting started, why YoCache, server & client
  configuration, FAQ. Published to GitHub Pages on every push to main that
  touches site/, independent of versioned releases.
• Every server flag can now be set via a YOCACHE_<FLAG> environment
  variable (e.g. YOCACHE_DATA_DIR, YOCACHE_ADDR), with CLI flags still
  taking precedence over env vars over compiled-in defaults — the config
  path Docker and systemd deployments expect.
• --hashequiv-addr (default :6767, on by default) opens a second,
  dedicated raw-TCP listener speaking bitbake's legacy OEHASHEQUIV wire
  protocol directly (no WebSocket), for pre-Scarthgap bitbake (Dunfell and
  earlier) whose hash-equivalence client can't speak ws://. Point
  BB_HASHSERVE at host:6767 to use it instead of
  ws://host:6768/hashequiv; pass --hashequiv-addr "" to disable it.
• GET /api/stats (and the startup "cache inventory" log line) now report
  hash-equivalence store size: hashequiv_taskhashes (recorded
  taskhash->unihash mappings), hashequiv_unihashes (distinct unihashes,
  the dedup signal), and hashequiv_outhashes (recorded outhash records).
• meta-yocache now declares every Yocto release from dunfell through
  wrynose in LAYERSERIES_COMPAT_yocache, closing the gap between the
  previously-declared dunfell/kirkstone/wrynose.

Changed

• Breaking: the five path flags (--db, --downloads, --sstate,
  --ledger, --access-log) are replaced by a single --data-dir (default
  var, same on-disk layout underneath: yocache.db, downloads/, sstate/,
  yocache.ledger.jsonl, yocache.access.jsonl). Anything passing the old
  flags needs to switch to --data-dir pointing at one root — this also
  clears the way for a single Docker volume mount instead of five.

Full Changelog: v0.1.6...v0.1.7