v0.3.2

v0.3.2 Release Notes

A spoke-onboarding bug-fix release on top of v0.3.1. No breaking changes —
existing installs keep working without any manual step.

Highlights

• Fresh spoke no longer reports count: 0 after joining a populated mesh
  (#133, PR #134). When a newly provisioned spoke connects, zenoh replicates the
  existing memories into its rocksdb, but status / search used to report
  count: 0 until kioku-mesh --rebuild status was run by hand — the local
  SQLite index is only backfilled by an explicit rebuild, and the replication
  subscriber ingests only new writes. get_index() now rebuilds once when the
  index is empty, even under the one-shot CLI's default skip (#38), so a fresh
  spoke self-heals. Explicit opt-outs (set_rebuild_on_init_explicit(False) /
  MESH_MEM_SKIP_REBUILD=1) are honored and the populated-index fast path is
  unchanged.
• kioku-mesh init --mode spoke now tells you the next step (#133, PR #134).
  The completion output points at the one-time kioku-mesh --rebuild status, so
  the empty-index count: 0 state during onboarding is self-explanatory.
• kioku-mesh init --install-systemd reuses an existing config (#133,
  PR #134). Installing the systemd unit on top of an already-provisioned
  zenohd.json5 no longer errors with "already exists, use --force" nor rewrites
  the config; it reuses the existing config unchanged and only generates the
  unit. --force still overwrites the config when explicitly requested.

Upgrade

No breaking changes.

uv tool install --upgrade git+https://github.com/h-wata/kioku-mesh.git
# or, from PyPI:
pip install --upgrade kioku-mesh

After upgrading on a spoke that previously showed count: 0, the next index
access (any status / search, or an agent connecting via the MCP server)
backfills automatically; no manual --rebuild is required.