Metadata-Version: 2.4
Name: hermes-plugin-qdrant-memory
Version: 0.7.0
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.0: one inspectable, repairable Qdrant policy

Runtime 0.7.0 makes a new installation and an in-place upgrade converge on the
same Qdrant policy. The default stays dense retrieval with float32 vectors.
An upgrade does not move a collection, re-embed memories, change memory
identity or change recall and write semantics.

The release adds a Runtime policy record for each profile destination. The
record states the target definition, the accepted effective policy and the
observed payload indexes. It is separate from point payloads. The existing
`schema_version=1` and the embedding identity sentinel are not migrated or
rewritten.

## Operator upgrade commands

Both operator entries share one implementation:

```sh
qdrant-memory --home PROFILE upgrade plan
qdrant-memory --home PROFILE upgrade apply --plan PLAN_ID
qdrant-memory --home PROFILE upgrade resume --plan PLAN_ID
qdrant-memory --home PROFILE upgrade status

hermes qdrant-memory upgrade plan
hermes qdrant-memory upgrade apply --plan PLAN_ID
```

`plan` and `status` never initialize a collection, write the Ledger, run
recovery, create an index or change configuration. `plan` saves one control
plane record so `apply` can reference it. Add `--dry-run` to inspect without
saving.

`apply` and `resume` take the existing writer lease and re-validate the saved
plan against the live profile. A stale plan is refused. A destination with
pending reset, scoped deletion, shared receipt or failed event work is refused
until the existing recovery path clears it.

## Payload index policy

The managed index set comes from one definition that `init`, `doctor`,
`upgrade plan` and `upgrade apply` all read. Existing collections keep their
indexes. Runtime no longer backfills them during normal startup, a plain
`init` or an MCP connection.

`upgrade apply` creates only missing managed indexes. A conflicting index type
is a blocker with an operator procedure. An extra index outside the policy is
reported and never removed. Embedded storage reports payload indexes as not
applicable instead of simulating them.

## Recovery and rollback

An embedded upgrade copies the closed local store, the Ledger, the delete and
reset receipts and the profile configuration into a recovery point. It then
reopens the copy and compares the point count before it continues.

A remote upgrade requires `--confirm-writers-isolated` and
`--accept-operator-backup`. Without both flags the Runtime refuses the apply.
This release does not hold Qdrant administrative backup rights.

An application version rollback is not a storage downgrade. Do not open data
written by a newer server with an older server or an older embedded client.
Restore the whole recovery point taken at the same stopped-writer boundary.
Writes that landed after that point are lost by design.

## Qdrant versions

Qdrant Server 1.20.1 is the recommended and rehearsed self-hosted baseline. The
controlled Runtime environment pins `qdrant-client==1.20.0`. The published
dependency range stays `qdrant-client>=1.15,<2`, so a bare PyPI install can
resolve another client within that range. Only the controlled environment and
the release acceptance run are exact pins.

The upgrade rehearsal keeps the 1.20.0 image as a fixture. It upgrades one
volume in place, copies the stopped volume and restores it into a fresh
volume. It then compares points, payloads, vectors and indexes.

Server and Cloud are inspected for version, capability and permission only.
An unknown version reports `unknown` and its limited capability. Embedded keeps
its local backend and has no independent server.

## Not in this release

Cross-collection copy or re-embed, alias switching, BM25 or RRF recall, MMR,
recency ranking, ACORN, tenant or HNSW graph control, quantization and sparse
backfill are future work. Diagnostics may report a probed capability. Nothing
is enabled automatically.

## Installation

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

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

For Hermes Catalog installations, wait for the separately reviewed Catalog
repin, run `hermes plugins update qdrant-memory`, and restart Hermes. A Runtime
publication does not update the Catalog automatically.

## Upgrade notes

From 0.6.3 or 0.6.2, keep the same profile, collection and embedding pipeline.
An existing destination keeps serving its dense path and is reported as
`legacy` until an operator applies a plan. Run `upgrade plan`, review the
blockers and the index status, then apply inside a short maintenance window.

Catalog users upgrading from 0.5.4 must keep the same embedding pipeline to
reuse a collection. The optional CPU FastEmbed extra changed from 0.9.0 to
0.9.1, which changes its embedding fingerprint even with the same model and
dimensions. Preserve the old environment and data. Do not infer reuse from
matching dimensions and do not overwrite the identity sentinel.

See the [0.6.3 release](0.6.3.md) for the preceding Runtime changes.
