hermes-plugin-qdrant-memory 0.5.2__tar.gz → 0.5.4__tar.gz

{hermes_plugin_qdrant_memory-0.5.2/hermes_plugin_qdrant_memory.egg-info → hermes_plugin_qdrant_memory-0.5.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hermes-plugin-qdrant-memory
-Version: 0.5.2
+Version: 0.5.4
 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
@@ -38,7 +38,7 @@ Skills—with explicit access control, conflict-safe updates, and crash recovery
 Shared deployment hardening in this checkout is documented in the
 [protected destination guide](docs/shared-memory/deployment-security.md) and
 [versioned threat model](docs/shared-memory/threat-model-v1.md). These additions
-are included in Runtime 0.5.2. Remote access needs the `[remote]` extra.
+are included in Runtime 0.5.4. Remote access needs the `[remote]` extra.
 
 ## One Memory, Multiple Agents — opt-in shared owner
 
@@ -51,19 +51,21 @@ Runtime 0.5.0 adds an opt-in authenticated local shared owner and stdio bridge.
 [![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 
-> **Runtime 0.5.2** keeps the opt-in authenticated local shared owner and the stdio
+> **Runtime 0.5.4** keeps the opt-in authenticated local shared owner and the stdio
 > bridge for explicit shared memory. It keeps the optional offline CPU embedding,
 > trusted setup and MCP Python SDK 1.x/2.x support from 0.3.0.
 > Explicit writes retain canonical-text deduplication without an LLM.
 > This patch makes a restart-interrupted write replayable with the same request
-> identifier. It changes no schema and no collection identity.
-> This guide selects Runtime 0.5.2. Check its availability on
-> [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.5.2/) before installation.
+> identifier. This patch fixes partially initialized providers after startup failures,
+> protects required checkpoints, and preserves WriterLease ownership through cleanup.
+> It changes no schema or collection identity. This guide selects Runtime 0.5.4.
+> Check its availability on
+> [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.5.4/) before installation.
 > The generic MCP distribution and managed launcher select their own exact Runtime
 > dependency and are released independently.
 > The Hermes Plugin Catalog has its own reviewed immutable pin. A PyPI release
 > does not upgrade it. One writer per destination remains required.
-> See [release notes](docs/releases/0.5.2.md) and [validation](docs/validation.md).
+> See [release notes](docs/releases/0.5.4.md) and [validation](docs/validation.md).
 
 [English](README.md) | [简体中文](README.zh-CN.md)
 
@@ -81,7 +83,7 @@ as a community-maintained plugin.
 ## How it works
 
 For non-Hermes users, install in a private Python 3.11+
-environment: `pip install 'hermes-plugin-qdrant-memory[mcp]==0.5.2'` (omit `[mcp]`
+environment: `pip install 'hermes-plugin-qdrant-memory[mcp]==0.5.4'` (omit `[mcp]`
 for CLI only). `qdrant-memory` is the CLI and `mcp` is its server subcommand.
 Standalone does not require Hermes. See [setup and quick start](docs/standalone.md).
 MCP-focused agents may instead use the [metadata-only distribution](https://github.com/cnkang/qdrant-memory-mcp).
@@ -185,7 +187,7 @@ Choose the **active profile's** home explicitly. Do not reuse another profile's
 **Catalog option: install the version reviewed by the official Hermes Plugin Catalog.**
 
 The Catalog selects its own fixed revision, which may be older than Runtime
-0.5.2. To use the current release, including opt-in shared memory, follow the
+0.5.4. To use the current release, including opt-in shared memory, follow the
 recommended version-locked installation below.
 
 ```bash
@@ -203,7 +205,7 @@ The install resolves the catalog's reviewed commit and prints the entry's declar
 tools, requirements and known issues before it clones anything.
 `hermes plugins enable` prepares the declared dependencies through Hermes PM.
 
-**Recommended: install the version-locked Runtime 0.5.2 source through the Hermes CLI.**
+**Recommended: install the version-locked Runtime 0.5.4 source through the Hermes CLI.**
 
 This immutable source revision includes opt-in shared memory. It does not depend
 on a PyPI release or a catalog update.
@@ -213,25 +215,26 @@ export HERMES_HOME="/absolute/path/to/your/hermes-profile"
 ollama pull qwen3-embedding:4b
 # Start Ollama if it is not running. Keep its service available.
 hermes plugins install https://github.com/cnkang/hermes-plugin-qdrant-memory \
-  --ref 604793341226e45f04500cd1d53fd668ddf89d63   # Runtime 0.5.2 release
+  --ref b293b953de7aa4715ccb3fed63e8cc64bda7443c   # Runtime 0.5.4 release
 hermes plugins enable qdrant-memory
 hermes memory setup
 hermes config set memory.provider qdrant-memory
 hermes qdrant-memory init
 ```
 
-**Previous verified source: install Runtime 0.3.0 through the Hermes CLI.**
+**Previous verified source: install Runtime 0.5.3 through the Hermes CLI.**
 
-This older immutable source revision includes optional CPU embedding and guided
-setup, but it predates opt-in shared memory. For the current release use
-Runtime 0.5.2 above. It does not depend on a PyPI release or a catalog update.
+This earlier verified source revision includes the provider lifecycle fix and
+opt-in shared memory, but it predates the 0.5.4 maintainability changes. For the
+current release use Runtime 0.5.4 above. It does not depend on a PyPI release or
+a catalog update.
 
 ```bash
 export HERMES_HOME="/absolute/path/to/your/hermes-profile"
 ollama pull qwen3-embedding:4b
 # Start Ollama if it is not running. Keep its service available.
 hermes plugins install https://github.com/cnkang/hermes-plugin-qdrant-memory \
-  --ref 534562f1df43541dbf906d248bb11cd085b211ee   # verified Runtime 0.3.0 source
+  --ref 0c83c2279ddd62f1aba98657aecc14a71a3dbf73   # verified Runtime 0.5.3 source
 hermes plugins enable qdrant-memory
 hermes memory setup
 hermes config set memory.provider qdrant-memory
@@ -248,7 +251,7 @@ environment. Omit `--ref` to track `main`, the development line.
 **Historical release: clone a published tag manually.**
 
 The v0.1.0 tag below predates the standalone interfaces and the explicit-write
-fix. Use the pinned source above for Runtime 0.5.2.
+fix. Use the pinned source above for Runtime 0.5.4.
 
 ```bash
 export HERMES_HOME="/absolute/path/to/your/hermes-profile"
@@ -566,6 +569,9 @@ Run Ruff lint and format checks before you commit. Install the repository
 pre-commit hook as described in [development setup](docs/development.md). The hook
 checks the staged snapshot. CI runs lint, both Python versions, Snyk and
 SonarCloud. See [CI services](docs/ci.md) for the tested host versions and lanes.
+The staged [soak system](docs/testing/soak.md) runs real Owner, Gateway, Ledger
+and Qdrant windows on x64 and ARM64 runners, and admits a five-hour matrix only
+after the short matrix passes.
 
 Build isolated dependency environments with Hermes PM. Then run the host's
 canonical test runner against this repository's tests. The tests import the real

{hermes_plugin_qdrant_memory-0.5.2 → hermes_plugin_qdrant_memory-0.5.4}/README.md

@@ -11,7 +11,7 @@ Skills—with explicit access control, conflict-safe updates, and crash recovery
 Shared deployment hardening in this checkout is documented in the
 [protected destination guide](docs/shared-memory/deployment-security.md) and
 [versioned threat model](docs/shared-memory/threat-model-v1.md). These additions
-are included in Runtime 0.5.2. Remote access needs the `[remote]` extra.
+are included in Runtime 0.5.4. Remote access needs the `[remote]` extra.
 
 ## One Memory, Multiple Agents — opt-in shared owner
 
@@ -24,19 +24,21 @@ Runtime 0.5.0 adds an opt-in authenticated local shared owner and stdio bridge.
 [![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 
-> **Runtime 0.5.2** keeps the opt-in authenticated local shared owner and the stdio
+> **Runtime 0.5.4** keeps the opt-in authenticated local shared owner and the stdio
 > bridge for explicit shared memory. It keeps the optional offline CPU embedding,
 > trusted setup and MCP Python SDK 1.x/2.x support from 0.3.0.
 > Explicit writes retain canonical-text deduplication without an LLM.
 > This patch makes a restart-interrupted write replayable with the same request
-> identifier. It changes no schema and no collection identity.
-> This guide selects Runtime 0.5.2. Check its availability on
-> [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.5.2/) before installation.
+> identifier. This patch fixes partially initialized providers after startup failures,
+> protects required checkpoints, and preserves WriterLease ownership through cleanup.
+> It changes no schema or collection identity. This guide selects Runtime 0.5.4.
+> Check its availability on
+> [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.5.4/) before installation.
 > The generic MCP distribution and managed launcher select their own exact Runtime
 > dependency and are released independently.
 > The Hermes Plugin Catalog has its own reviewed immutable pin. A PyPI release
 > does not upgrade it. One writer per destination remains required.
-> See [release notes](docs/releases/0.5.2.md) and [validation](docs/validation.md).
+> See [release notes](docs/releases/0.5.4.md) and [validation](docs/validation.md).
 
 [English](README.md) | [简体中文](README.zh-CN.md)
 
@@ -54,7 +56,7 @@ as a community-maintained plugin.
 ## How it works
 
 For non-Hermes users, install in a private Python 3.11+
-environment: `pip install 'hermes-plugin-qdrant-memory[mcp]==0.5.2'` (omit `[mcp]`
+environment: `pip install 'hermes-plugin-qdrant-memory[mcp]==0.5.4'` (omit `[mcp]`
 for CLI only). `qdrant-memory` is the CLI and `mcp` is its server subcommand.
 Standalone does not require Hermes. See [setup and quick start](docs/standalone.md).
 MCP-focused agents may instead use the [metadata-only distribution](https://github.com/cnkang/qdrant-memory-mcp).
@@ -158,7 +160,7 @@ Choose the **active profile's** home explicitly. Do not reuse another profile's
 **Catalog option: install the version reviewed by the official Hermes Plugin Catalog.**
 
 The Catalog selects its own fixed revision, which may be older than Runtime
-0.5.2. To use the current release, including opt-in shared memory, follow the
+0.5.4. To use the current release, including opt-in shared memory, follow the
 recommended version-locked installation below.
 
 ```bash
@@ -176,7 +178,7 @@ The install resolves the catalog's reviewed commit and prints the entry's declar
 tools, requirements and known issues before it clones anything.
 `hermes plugins enable` prepares the declared dependencies through Hermes PM.
 
-**Recommended: install the version-locked Runtime 0.5.2 source through the Hermes CLI.**
+**Recommended: install the version-locked Runtime 0.5.4 source through the Hermes CLI.**
 
 This immutable source revision includes opt-in shared memory. It does not depend
 on a PyPI release or a catalog update.
@@ -186,25 +188,26 @@ export HERMES_HOME="/absolute/path/to/your/hermes-profile"
 ollama pull qwen3-embedding:4b
 # Start Ollama if it is not running. Keep its service available.
 hermes plugins install https://github.com/cnkang/hermes-plugin-qdrant-memory \
-  --ref 604793341226e45f04500cd1d53fd668ddf89d63   # Runtime 0.5.2 release
+  --ref b293b953de7aa4715ccb3fed63e8cc64bda7443c   # Runtime 0.5.4 release
 hermes plugins enable qdrant-memory
 hermes memory setup
 hermes config set memory.provider qdrant-memory
 hermes qdrant-memory init
 ```
 
-**Previous verified source: install Runtime 0.3.0 through the Hermes CLI.**
+**Previous verified source: install Runtime 0.5.3 through the Hermes CLI.**
 
-This older immutable source revision includes optional CPU embedding and guided
-setup, but it predates opt-in shared memory. For the current release use
-Runtime 0.5.2 above. It does not depend on a PyPI release or a catalog update.
+This earlier verified source revision includes the provider lifecycle fix and
+opt-in shared memory, but it predates the 0.5.4 maintainability changes. For the
+current release use Runtime 0.5.4 above. It does not depend on a PyPI release or
+a catalog update.
 
 ```bash
 export HERMES_HOME="/absolute/path/to/your/hermes-profile"
 ollama pull qwen3-embedding:4b
 # Start Ollama if it is not running. Keep its service available.
 hermes plugins install https://github.com/cnkang/hermes-plugin-qdrant-memory \
-  --ref 534562f1df43541dbf906d248bb11cd085b211ee   # verified Runtime 0.3.0 source
+  --ref 0c83c2279ddd62f1aba98657aecc14a71a3dbf73   # verified Runtime 0.5.3 source
 hermes plugins enable qdrant-memory
 hermes memory setup
 hermes config set memory.provider qdrant-memory
@@ -221,7 +224,7 @@ environment. Omit `--ref` to track `main`, the development line.
 **Historical release: clone a published tag manually.**
 
 The v0.1.0 tag below predates the standalone interfaces and the explicit-write
-fix. Use the pinned source above for Runtime 0.5.2.
+fix. Use the pinned source above for Runtime 0.5.4.
 
 ```bash
 export HERMES_HOME="/absolute/path/to/your/hermes-profile"
@@ -539,6 +542,9 @@ Run Ruff lint and format checks before you commit. Install the repository
 pre-commit hook as described in [development setup](docs/development.md). The hook
 checks the staged snapshot. CI runs lint, both Python versions, Snyk and
 SonarCloud. See [CI services](docs/ci.md) for the tested host versions and lanes.
+The staged [soak system](docs/testing/soak.md) runs real Owner, Gateway, Ledger
+and Qdrant windows on x64 and ARM64 runners, and admits a five-hour matrix only
+after the short matrix passes.
 
 Build isolated dependency environments with Hermes PM. Then run the host's
 canonical test runner against this repository's tests. The tests import the real

{hermes_plugin_qdrant_memory-0.5.2 → hermes_plugin_qdrant_memory-0.5.4}/docs/local-embedding.md

@@ -35,11 +35,11 @@ python -m pip install '.[mcp,local]'
 
 For a published package, install the same extras with the release version:
 
-Check [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.5.2/) for
-Runtime 0.5.2 availability before running this command.
+Check [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.5.4/) for
+Runtime 0.5.4 availability before running this command.
 
 ```sh
-python -m pip install 'hermes-plugin-qdrant-memory[mcp,local]==0.5.2'
+python -m pip install 'hermes-plugin-qdrant-memory[mcp,local]==0.5.4'
 ```
 
 Choose **one** setup command and replace the profile path with a new absolute

{hermes_plugin_qdrant_memory-0.5.2 → hermes_plugin_qdrant_memory-0.5.4/hermes_plugin_qdrant_memory.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hermes-plugin-qdrant-memory
-Version: 0.5.2
+Version: 0.5.4
 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
@@ -38,7 +38,7 @@ Skills—with explicit access control, conflict-safe updates, and crash recovery
 Shared deployment hardening in this checkout is documented in the
 [protected destination guide](docs/shared-memory/deployment-security.md) and
 [versioned threat model](docs/shared-memory/threat-model-v1.md). These additions
-are included in Runtime 0.5.2. Remote access needs the `[remote]` extra.
+are included in Runtime 0.5.4. Remote access needs the `[remote]` extra.
 
 ## One Memory, Multiple Agents — opt-in shared owner
 
@@ -51,19 +51,21 @@ Runtime 0.5.0 adds an opt-in authenticated local shared owner and stdio bridge.
 [![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 
-> **Runtime 0.5.2** keeps the opt-in authenticated local shared owner and the stdio
+> **Runtime 0.5.4** keeps the opt-in authenticated local shared owner and the stdio
 > bridge for explicit shared memory. It keeps the optional offline CPU embedding,
 > trusted setup and MCP Python SDK 1.x/2.x support from 0.3.0.
 > Explicit writes retain canonical-text deduplication without an LLM.
 > This patch makes a restart-interrupted write replayable with the same request
-> identifier. It changes no schema and no collection identity.
-> This guide selects Runtime 0.5.2. Check its availability on
-> [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.5.2/) before installation.
+> identifier. This patch fixes partially initialized providers after startup failures,
+> protects required checkpoints, and preserves WriterLease ownership through cleanup.
+> It changes no schema or collection identity. This guide selects Runtime 0.5.4.
+> Check its availability on
+> [PyPI](https://pypi.org/project/hermes-plugin-qdrant-memory/0.5.4/) before installation.
 > The generic MCP distribution and managed launcher select their own exact Runtime
 > dependency and are released independently.
 > The Hermes Plugin Catalog has its own reviewed immutable pin. A PyPI release
 > does not upgrade it. One writer per destination remains required.
-> See [release notes](docs/releases/0.5.2.md) and [validation](docs/validation.md).
+> See [release notes](docs/releases/0.5.4.md) and [validation](docs/validation.md).
 
 [English](README.md) | [简体中文](README.zh-CN.md)
 
@@ -81,7 +83,7 @@ as a community-maintained plugin.
 ## How it works
 
 For non-Hermes users, install in a private Python 3.11+
-environment: `pip install 'hermes-plugin-qdrant-memory[mcp]==0.5.2'` (omit `[mcp]`
+environment: `pip install 'hermes-plugin-qdrant-memory[mcp]==0.5.4'` (omit `[mcp]`
 for CLI only). `qdrant-memory` is the CLI and `mcp` is its server subcommand.
 Standalone does not require Hermes. See [setup and quick start](docs/standalone.md).
 MCP-focused agents may instead use the [metadata-only distribution](https://github.com/cnkang/qdrant-memory-mcp).
@@ -185,7 +187,7 @@ Choose the **active profile's** home explicitly. Do not reuse another profile's
 **Catalog option: install the version reviewed by the official Hermes Plugin Catalog.**
 
 The Catalog selects its own fixed revision, which may be older than Runtime
-0.5.2. To use the current release, including opt-in shared memory, follow the
+0.5.4. To use the current release, including opt-in shared memory, follow the
 recommended version-locked installation below.
 
 ```bash
@@ -203,7 +205,7 @@ The install resolves the catalog's reviewed commit and prints the entry's declar
 tools, requirements and known issues before it clones anything.
 `hermes plugins enable` prepares the declared dependencies through Hermes PM.
 
-**Recommended: install the version-locked Runtime 0.5.2 source through the Hermes CLI.**
+**Recommended: install the version-locked Runtime 0.5.4 source through the Hermes CLI.**
 
 This immutable source revision includes opt-in shared memory. It does not depend
 on a PyPI release or a catalog update.
@@ -213,25 +215,26 @@ export HERMES_HOME="/absolute/path/to/your/hermes-profile"
 ollama pull qwen3-embedding:4b
 # Start Ollama if it is not running. Keep its service available.
 hermes plugins install https://github.com/cnkang/hermes-plugin-qdrant-memory \
-  --ref 604793341226e45f04500cd1d53fd668ddf89d63   # Runtime 0.5.2 release
+  --ref b293b953de7aa4715ccb3fed63e8cc64bda7443c   # Runtime 0.5.4 release
 hermes plugins enable qdrant-memory
 hermes memory setup
 hermes config set memory.provider qdrant-memory
 hermes qdrant-memory init
 ```
 
-**Previous verified source: install Runtime 0.3.0 through the Hermes CLI.**
+**Previous verified source: install Runtime 0.5.3 through the Hermes CLI.**
 
-This older immutable source revision includes optional CPU embedding and guided
-setup, but it predates opt-in shared memory. For the current release use
-Runtime 0.5.2 above. It does not depend on a PyPI release or a catalog update.
+This earlier verified source revision includes the provider lifecycle fix and
+opt-in shared memory, but it predates the 0.5.4 maintainability changes. For the
+current release use Runtime 0.5.4 above. It does not depend on a PyPI release or
+a catalog update.
 
 ```bash
 export HERMES_HOME="/absolute/path/to/your/hermes-profile"
 ollama pull qwen3-embedding:4b
 # Start Ollama if it is not running. Keep its service available.
 hermes plugins install https://github.com/cnkang/hermes-plugin-qdrant-memory \
-  --ref 534562f1df43541dbf906d248bb11cd085b211ee   # verified Runtime 0.3.0 source
+  --ref 0c83c2279ddd62f1aba98657aecc14a71a3dbf73   # verified Runtime 0.5.3 source
 hermes plugins enable qdrant-memory
 hermes memory setup
 hermes config set memory.provider qdrant-memory
@@ -248,7 +251,7 @@ environment. Omit `--ref` to track `main`, the development line.
 **Historical release: clone a published tag manually.**
 
 The v0.1.0 tag below predates the standalone interfaces and the explicit-write
-fix. Use the pinned source above for Runtime 0.5.2.
+fix. Use the pinned source above for Runtime 0.5.4.
 
 ```bash
 export HERMES_HOME="/absolute/path/to/your/hermes-profile"
@@ -566,6 +569,9 @@ Run Ruff lint and format checks before you commit. Install the repository
 pre-commit hook as described in [development setup](docs/development.md). The hook
 checks the staged snapshot. CI runs lint, both Python versions, Snyk and
 SonarCloud. See [CI services](docs/ci.md) for the tested host versions and lanes.
+The staged [soak system](docs/testing/soak.md) runs real Owner, Gateway, Ledger
+and Qdrant windows on x64 and ARM64 runners, and admits a five-hour matrix only
+after the short matrix passes.
 
 Build isolated dependency environments with Hermes PM. Then run the host's
 canonical test runner against this repository's tests. The tests import the real

{hermes_plugin_qdrant_memory-0.5.2 → hermes_plugin_qdrant_memory-0.5.4}/hermes_plugin_qdrant_memory.egg-info/SOURCES.txt

@@ -66,6 +66,7 @@ tests/test_ci_gate.py
 tests/test_ci_infrastructure_retry.py
 tests/test_cli_output.py
 tests/test_config_embedding.py
+tests/test_cross_process_lifecycle_recovery.py
 tests/test_deletion_ordering.py
 tests/test_dependency_inputs.py
 tests/test_dependency_security.py
@@ -74,6 +75,7 @@ tests/test_explicit_dedupe.py
 tests/test_fastembed_compat.py
 tests/test_host_lifecycle.py
 tests/test_host_pins.py
+tests/test_initialization_failures.py
 tests/test_input_validation.py
 tests/test_inventory_export.py
 tests/test_live_metrics.py
@@ -128,6 +130,10 @@ tests/security/test_cloud_owner_cleanup.py
 tests/security/test_device_server.py
 tests/security/test_shared_security.py
 tests/security/test_shared_security_live.py
+tests/soak/test_harness.py
+tests/soak/test_invariants.py
+tests/soak/test_supervisor.py
+tests/soak/test_workflow_gates.py
 tests/standalone/__init__.py
 tests/standalone/test_admission_control.py
 tests/standalone/test_device_grants.py

{hermes_plugin_qdrant_memory-0.5.2 → hermes_plugin_qdrant_memory-0.5.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "hermes-plugin-qdrant-memory"
-version = "0.5.2"
+version = "0.5.4"
 description = "Durable Qdrant memory for Hermes, standalone CLI and local MCP"
 readme = "README.md"
 license = "MIT"