YantrikDB

Surface-parity hotfix between the engine and pyo3 bindings.

Why

Engine v0.7.2 (commits dd94ace + 45e11e2) shipped YantrikDB::with_default() + record_text() + recall_text() so default pip install yantrikdb users could use the bundled potion-base-2M embedder without an external sentence-transformers install or first-run model download. The pyo3 bindings in crates/yantrikdb-python hadn't been updated to match — the wheel exposed 50+ methods but no *_text variants and no constructor that picked up the bundled embedder automatically. Default Python users still saw NoEmbedder unless they manually passed embedding_dim=64.

Diagnosed by a downstream plugin workspace's wheel introspection, fixed directly in the engine repo (~110 LOC, no engine code changes).

What's new in Python

from yantrikdb import YantrikDB

# v0.7.4 — Just Works, no extra deps:
db = YantrikDB.with_default("./mem.db")
db.record_text("Alice loves Rust", "semantic")
results = db.recall_text("rust enthusiast", top_k=5)

# Existing path (record(text=...) auto-embeds when embedder attached):
db.record(text="Bob prefers Python", memory_type="semantic")

API additions

| Method | Mirrors | Purpose |
|--------|---------|---------|
| YantrikDB.with_default(db_path) | YantrikDB::with_default | Open at BUNDLED_EMBEDDER_DIM (64), bundled embedder auto-attached |
| db.has_embedder() | YantrikDB::has_embedder | Introspect whether a Rust-native embedder is configured |
| db.record_text(text, ...) | YantrikDB::record_text | Auto-embed via engine's configured embedder |
| db.recall_text(query, top_k=10) | YantrikDB::recall_text | Auto-embed; same defaults as Rust API |

Compatibility

Pure-additive. No existing API touched, no breaking change. Existing record(text=..., embedding=None) and recall(query=...) paths continue to work unchanged.

🤖 Generated with Claude Code