Metadata-Version: 2.4
Name: hermes-plugin-qdrant-memory
Version: 0.7.2
Summary: Durable Qdrant memory for Hermes, standalone CLI and local MCP
License-Expression: MIT
Project-URL: Homepage, https://github.com/cnkang/hermes-plugin-qdrant-memory
Project-URL: Repository, https://github.com/cnkang/hermes-plugin-qdrant-memory
Project-URL: Issues, https://github.com/cnkang/hermes-plugin-qdrant-memory/issues
Project-URL: Changelog, https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/CHANGELOG.md
Project-URL: MCP, https://github.com/cnkang/qdrant-memory-mcp
Project-URL: Skill, https://github.com/cnkang/skills/tree/main/qdrant-memory
Requires-Python: >=3.11
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: qdrant-client<2,>=1.15
Requires-Dist: httpx<1,>=0.28
Requires-Dist: portalocker<4,>=3.2
Requires-Dist: jsonschema<5,>=4.23
Requires-Dist: pywin32<313,>=311; sys_platform == "win32"
Provides-Extra: mcp
Requires-Dist: mcp<3,>=1.30; extra == "mcp"
Provides-Extra: remote
Requires-Dist: mcp<3,>=1.30; extra == "remote"
Requires-Dist: uvicorn<1,>=0.35; extra == "remote"
Provides-Extra: local
Requires-Dist: fastembed==0.9.1; extra == "local"
Dynamic: license-file

# Runtime 0.7.2: retain the upgrade recovery point after local writes

Runtime 0.7.2 carries the upgrade-plan write-watermark protection merged in
Runtime PR #148. It preserves the existing retrieval behavior, point identity,
stored payloads, embedding configuration, authorization rules and four scoped
MCP tools.

## A plan cannot resume across a local Runtime write

Each saved upgrade plan records the current write watermark from its profile's
local Ledger. `apply` and `resume` compare that value again while holding the
profile writer lease. If this Runtime committed a write after the plan was
created, `status` reports `write_since_plan`, and `resume` refuses to continue
with the old plan.

The refusal keeps the old plan and its backup reference available for review.
An operator can explicitly run `upgrade plan --replace` to archive that plan
and backup reference before creating a fresh plan. A plan saved by a Runtime
version without watermark support cannot resume, even when no local write
occurred, because it has no recorded watermark; explicitly replace that legacy
plan. For a plan that includes a watermark and has no local write across the
plan boundary, resuming an interrupted upgrade reuses its recorded embedded
backup only while that backup still exists and passes verification, instead of
creating a second recovery point. If the recorded backup is missing or unusable,
resume first attempts to recover a verified backup for the same plan instance.
If none can be recovered, it stops before further target changes and requires
`upgrade plan --replace`.

**Scope boundary:** the watermark observes writes recorded by this Runtime in
the local profile Ledger. It cannot observe another Runtime process using a
separate Ledger, another profile or device, or direct writes from other clients
to Qdrant. It does not protect an entire Qdrant Cloud destination. Stop or
isolate every other writer and take the provider's normal snapshot before an
upgrade that requires a stable destination.

The watermark does not migrate data, change embedding models or dimensions,
rebuild the collection, or change retrieval defaults. It is upgrade-plan
protection only.

## Compatibility

Runtime 0.7.2 keeps the existing storage and policy schemas. Existing memories
remain in place. No migration, re-embedding or index rebuild is required.
Hermes Catalog and the independent MCP distribution keep their own pins; this
release preparation does not change either pin.

## Installation

Check [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.7.2/) for
availability before installing in a private environment:

```sh
python -m pip install 'hermes-plugin-qdrant-memory[mcp]==0.7.2'
```

For an existing destination, review `upgrade status` and `upgrade plan` before
applying. Keep the original plan identifier when resuming a watermark-enabled
interrupted upgrade that is not stale. Plans saved before watermark support
must be replaced even when no local write occurred. If a local write made a
supported plan stale, retain its recovery point and review the blockers before
explicitly replacing it.
