Metadata-Version: 2.4
Name: hermes-plugin-qdrant-memory
Version: 0.6.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.6.2: receipt-scoped failed-event recovery

Runtime 0.6.2 adds receipt-scoped recovery for lifecycle events that were
persisted but later marked `FAILED`. An authenticated retry validates the
event's stored operation plan, requeues only its failed operations and returns
the event to `PENDING`. It does not reset unrelated writes or re-extract the
turn. `QUARANTINED` events remain operator-controlled, and malformed plans fail
closed.

Runtime 0.6.1 behavior, the SQLite ledger format, Qdrant collection schema,
vector dimensions, embedding fingerprints, scope boundaries and writer leases
remain unchanged. No data migration or re-embedding is required. The Owner
lifecycle route remains opt-in and still requires its existing authorization
and scope checks.

## Install this release

Confirm version 0.6.2 is available on PyPI before installing:

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

This installs the standalone CLI and MCP base without Hermes. Add the `local`
extra for optional CPU embeddings or the `remote` extra for the authenticated
Owner service. Model preparation requires explicit approval. Configure a
private profile before memory operations. See the
[standalone guide](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/v0.6.2/docs/standalone.md),
[CPU setup](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/v0.6.2/docs/local-embedding.md)
and [Owner guide](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/v0.6.2/docs/shared-memory/remote-owner.md).

## Upgrade from 0.6.1

Install into the environment that already uses the intended private profile.
Keep the same profile, Qdrant collection and embedding pipeline. After upgrading,
run `qdrant-memory status` and `qdrant-memory verify` before resuming writes.
The release does not automatically retry failed events; a client must make an
authorized retry request for the same event receipt.

Publishing Runtime does not publish or update the generic MCP distribution,
Codex plugin, DSH bundle, WorkBuddy launcher or Hermes Plugin Catalog. Each
integration keeps its own version pin and release checks.
