Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[0.10.8] - 2026-07-15

MCP server orphan hardening — kumiho.mcp_server now exits when its launching ancestor chain dies: event-driven on Windows (a watchdog thread blocks on the ancestor process handles via WaitForMultipleObjects), ppid-reparent polling on POSIX. On Windows, MCP clients restart sessions by terminating the launcher process, which does not kill its children — and because a venv’s Scripts\python.exe is a redirector stub that runs the base interpreter as a separate child, the real server is a grandchild or deeper, so the whole contiguous python-named ancestor chain plus the client is watched, not just the direct parent. The stranded python -m kumiho.mcp_server processes previously accumulated without bound (KumihoIO/kumiho-plugins#25). Additionally, main() now hard-exits once the stdio transport closes, so lingering non-daemon threads (thread pools, gRPC channels) can never keep a dead server alive. Opt out with KUMIHO_MCP_DISABLE_ORPHAN_WATCHDOG=1.

tool_memory_store_batch — the bulk counterpart of tool_memory_store for the MCP write path. N captures land in one batch_create_revisions transaction (removing the neo4j relationship-group deadlock that per-capture concurrency triggers, and collapsing the heaviest create/revision writes) while preserving every per-capture semantic of the single path: credential screening, space resolution, fuzzy-stack, event_date/metadata, tags, topic bundle, and DERIVED_FROM edges (tag/bundle/edge stay per-item — the server has no batch RPC for them). kumiho_memory_reflect routes ≥2-capture writes through it; a single capture keeps the byte-identical per-capture path.

Batch revision creation — batch_create_revisions(revisions, idempotency_prefix=...) writes up to 200 captures (item + revision + optional artifacts) in a single server transaction, returning positional (results, failures). Missing items are auto-created from each row’s item_kref; rows targeting the same item stack in order (last becomes latest); per-row artifacts can mark one "default": True so the chain resolves straight from the item kref; a stable idempotency_prefix makes re-submission a safe no-op. Requires kumiho-server >= 1.6.3.

Full-text fuzzy search — search(query, ...) returns ranked items (SearchResult with item, score, matched_in), with automatic typo tolerance.
Semantic revision scoring — score_revisions(query, revision_krefs) scores revisions against a query using server-side embeddings and/or fulltext.
Batch revision fetch — batch_get_revisions(revision_krefs=..., item_krefs=..., tag=...) fetches many revisions in a single call, returning (revisions, not_found).
By-kref accessors — get_artifact_by_kref(), get_bundle_by_kref(), and client.get_item_from_revision().

The advanced event_stream() parameters (cursor, consumer_group, from_beginning) and get_event_capabilities() are now generally available.
The C++ and Dart SDKs now have full feature parity with the Python SDK.

Event streaming cursor support: Event.cursor attribute for resumable streaming
EventCapabilities API: get_event_capabilities() to query tier-based streaming features
New event_stream() parameters:
- cursor: Resume from last position (Creator+ tiers, Coming Soon)
- consumer_group: Load-balanced consumption (Enterprise tier, Coming Soon)
- from_beginning: Replay entire buffer (Creator+ tiers, Coming Soon)
Tier capability documentation with Coming Soon markers