v3.4.0

11cafe/jaazv3.4.0Jun 6, 2026by igorls

AI Summary

Introduces pluggable vector backends (Qdrant, pgvector, sqlite_exact), Docker support for the MCP server and CLI, and a migration tool for legacy wing names, alongside reliability fixes for embeddings and data loss prevention.

Key Highlights

Pluggable vector backends (Qdrant, pgvector, sqlite_exact) selectable via environment variables.
Docker images available for both the MCP server and CLI (CPU and GPU variants).
New `mempalace migrate-wings` command to normalize legacy wing names.
Fixes for embeddinggemma compatibility with ChromaDB 1.5.x and prevention of silent data loss.

New Features

Pluggable vector backends
Docker images (CPU + GPU)
Known-systems lexicon for entity detection
Trusted Publishing via GitHub Actions

Full Release Notes

## v3.4.0 — pluggable backends, Docker, and reliability fixes

### Features
- **Pluggable vector backends** — Qdrant, pgvector, and sqlite_exact alongside the default ChromaDB, selectable via `MEMPALACE_BACKEND` / `--backend`.
- **Docker images** (CPU + GPU) for the MCP server and CLI.
- **`mempalace migrate-wings`** — one-time migration that normalizes legacy wing names (strip leading/trailing separators) so pre-upgrade palaces stay discoverable. See `docs/recovery/wing-name-migration.md`.
- **Known-systems lexicon** keeps multi-word product names atomic in entity detection.

### Fixes
- embeddinggemma (the default model) now works with ChromaDB 1.5.x — semantic search was silently failing on fresh installs.
- Prevent silent data loss from `drawer_id` hash collisions.
- Importing `mcp_server` no longer recreates `~/.mempalace` (respects the privacy kill-switch).
- `diary_write` accepts a `content` alias and restores the missing-parameter diagnostic.
- Explicit-vector backends handle single-document inputs correctly.

### Infrastructure
- PyPI publishing via GitHub Actions **Trusted Publishing** (OIDC), gated by manual approval.