qdrant-memory-mcp 0.2.2__tar.gz → 0.2.4__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (129) hide show
  1. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/MANIFEST.in +4 -0
  2. {qdrant_memory_mcp-0.2.2/qdrant_memory_mcp.egg-info → qdrant_memory_mcp-0.2.4}/PKG-INFO +17 -18
  3. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/README.md +15 -16
  4. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/README.zh-CN.md +22 -16
  5. qdrant_memory_mcp-0.2.4/docs/ci.md +87 -0
  6. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/dsh-integration.md +6 -7
  7. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/dsh-integration.zh-CN.md +13 -8
  8. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/dsh-validation.md +29 -12
  9. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/publishing.md +5 -5
  10. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/quickstart.md +4 -4
  11. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/quickstart.zh-CN.md +5 -3
  12. qdrant_memory_mcp-0.2.4/docs/releases/0.1.2.md +20 -0
  13. qdrant_memory_mcp-0.2.4/docs/releases/0.1.2.zh-CN.md +18 -0
  14. qdrant_memory_mcp-0.2.4/docs/releases/0.1.3.md +33 -0
  15. qdrant_memory_mcp-0.2.4/docs/releases/0.1.3.zh-CN.md +28 -0
  16. qdrant_memory_mcp-0.2.4/docs/releases/0.1.4.md +45 -0
  17. qdrant_memory_mcp-0.2.4/docs/releases/0.1.4.zh-CN.md +34 -0
  18. qdrant_memory_mcp-0.2.4/docs/releases/0.2.0.md +20 -0
  19. qdrant_memory_mcp-0.2.4/docs/releases/0.2.1.md +21 -0
  20. qdrant_memory_mcp-0.2.4/docs/releases/0.2.3.md +24 -0
  21. qdrant_memory_mcp-0.2.4/docs/releases/0.2.3.zh-CN.md +22 -0
  22. qdrant_memory_mcp-0.2.4/docs/releases/0.2.4.md +24 -0
  23. qdrant_memory_mcp-0.2.4/docs/releases/0.2.4.zh-CN.md +21 -0
  24. qdrant_memory_mcp-0.2.4/docs/universal-owner-status.md +87 -0
  25. qdrant_memory_mcp-0.2.4/docs/universal-owner-status.zh-CN.md +86 -0
  26. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/workbuddy-one-click-architecture.md +1 -1
  27. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/workbuddy-one-click-validation.md +11 -9
  28. qdrant_memory_mcp-0.2.4/integrations/agent-hosts/package-lock.json +1809 -0
  29. qdrant_memory_mcp-0.2.4/integrations/agent-hosts/package.json +8 -0
  30. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/dsh/bundle/README.md +1 -1
  31. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/dsh/bundle/cordis.patch.yml +2 -2
  32. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/dsh/bundle/package.json +1 -1
  33. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/dsh/package-lock.json +10 -17
  34. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/dsh/package.json +6 -0
  35. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/dsh/qdrant-memory.cordis.yml +1 -1
  36. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/README.md +17 -5
  37. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/THIRD_PARTY_NOTICES.md +2 -0
  38. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/package.json +1 -1
  39. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/provision.mjs +34 -2
  40. qdrant_memory_mcp-0.2.4/integrations/managed/requirements.in +5 -0
  41. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/requirements.lock +87 -94
  42. qdrant_memory_mcp-0.2.4/integrations/managed/runtime.json +17 -0
  43. qdrant_memory_mcp-0.2.4/integrations/pi/README.md +107 -0
  44. qdrant_memory_mcp-0.2.4/integrations/pi/owner-memory.mjs +207 -0
  45. qdrant_memory_mcp-0.2.4/integrations/shared/README.md +117 -0
  46. qdrant_memory_mcp-0.2.4/integrations/shared/codex.remote-preview.toml +5 -0
  47. qdrant_memory_mcp-0.2.4/integrations/shared/dsh.remote-preview.cordis.yml +14 -0
  48. qdrant_memory_mcp-0.2.4/integrations/shared/mcp.remote-preview.json +10 -0
  49. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/README.md +20 -21
  50. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/connector-meta.json +1 -1
  51. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/mcp.json +1 -1
  52. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/mcp.uvx.json +1 -1
  53. qdrant_memory_mcp-0.2.4/integrations/workbuddy/skill-source.json +5 -0
  54. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/pyproject.toml +2 -2
  55. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4/qdrant_memory_mcp.egg-info}/PKG-INFO +17 -18
  56. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/qdrant_memory_mcp.egg-info/SOURCES.txt +25 -0
  57. qdrant_memory_mcp-0.2.4/qdrant_memory_mcp.egg-info/requires.txt +1 -0
  58. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/runtime-source.json +2 -2
  59. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/scripts/prepare_runtime.py +19 -2
  60. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/server.json +2 -2
  61. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/dsh_acceptance.py +41 -0
  62. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/managed-cold-acceptance.mjs +11 -2
  63. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_distribution.py +4 -4
  64. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_dsh_bundle.py +16 -4
  65. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_launcher_package.py +11 -0
  66. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_managed_bridge.py +11 -4
  67. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_managed_launcher.mjs +16 -1
  68. qdrant_memory_mcp-0.2.4/tests/test_native_pi_handoff.py +179 -0
  69. qdrant_memory_mcp-0.2.4/tests/test_pi_owner_extension.mjs +190 -0
  70. qdrant_memory_mcp-0.2.4/tests/test_pi_owner_host.mjs +63 -0
  71. qdrant_memory_mcp-0.2.4/tests/test_pi_owner_transport.mjs +53 -0
  72. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_protocol.py +1 -1
  73. qdrant_memory_mcp-0.2.4/tests/test_runtime_source.py +91 -0
  74. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_workbuddy_package.py +2 -2
  75. qdrant_memory_mcp-0.2.2/docs/ci.md +0 -59
  76. qdrant_memory_mcp-0.2.2/integrations/managed/requirements.in +0 -2
  77. qdrant_memory_mcp-0.2.2/integrations/managed/runtime.json +0 -9
  78. qdrant_memory_mcp-0.2.2/integrations/shared/README.md +0 -53
  79. qdrant_memory_mcp-0.2.2/integrations/workbuddy/skill-source.json +0 -5
  80. qdrant_memory_mcp-0.2.2/qdrant_memory_mcp.egg-info/requires.txt +0 -1
  81. qdrant_memory_mcp-0.2.2/tests/test_runtime_source.py +0 -36
  82. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/LICENSE +0 -0
  83. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/THIRD_PARTY_NOTICES.md +0 -0
  84. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/adr/0001-python-runtime-and-node-launcher.md +0 -0
  85. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/architecture.md +0 -0
  86. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/cross-harness-architecture.md +0 -0
  87. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/docs/hermes-compatibility.md +0 -0
  88. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/dsh/README.md +0 -0
  89. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/LICENSE +0 -0
  90. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/bootstrap.mjs +0 -0
  91. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/bridge.mjs +0 -0
  92. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/launcher.mjs +0 -0
  93. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/managed/tools.json +0 -0
  94. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/shared/codex.preview.toml +0 -0
  95. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/shared/dsh.preview.cordis.yml +0 -0
  96. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/shared/mcp.preview.json +0 -0
  97. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/build.py +0 -0
  98. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/icon.svg +0 -0
  99. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/mcp.managed-preview.json +0 -0
  100. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/public_install.py +0 -0
  101. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/integrations/workbuddy/release.py +0 -0
  102. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/qdrant_memory_mcp.egg-info/dependency_links.txt +0 -0
  103. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/qdrant_memory_mcp.egg-info/entry_points.txt +0 -0
  104. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/qdrant_memory_mcp.egg-info/top_level.txt +0 -0
  105. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/schemas/LICENSE +0 -0
  106. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/schemas/README.md +0 -0
  107. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/schemas/server.schema.json +0 -0
  108. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/scripts/dsh_bundle_release.py +0 -0
  109. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/scripts/pack_dsh_bundle.py +0 -0
  110. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/scripts/pack_launcher.py +0 -0
  111. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/scripts/pypi_release.py +0 -0
  112. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/scripts/registry_publish.py +0 -0
  113. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/scripts/verify_metadata.py +0 -0
  114. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/setup.cfg +0 -0
  115. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/dsh-client.mjs +0 -0
  116. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/dsh-reconnect-wrapper.mjs +0 -0
  117. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/managed-backend.mjs +0 -0
  118. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/public-launcher-acceptance.mjs +0 -0
  119. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_cross_harness.py +0 -0
  120. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_default_profile.py +0 -0
  121. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_dsh_bundle_release.py +0 -0
  122. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_launch_examples.py +0 -0
  123. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_managed_bootstrap.mjs +0 -0
  124. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_release_guards.py +0 -0
  125. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_release_versions.py +0 -0
  126. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_shared_preview_configs.py +0 -0
  127. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_workbuddy_mcp.py +0 -0
  128. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_workbuddy_public_install.py +0 -0
  129. {qdrant_memory_mcp-0.2.2 → qdrant_memory_mcp-0.2.4}/tests/test_workbuddy_release.py +0 -0
@@ -18,3 +18,7 @@ include docs/dsh-integration.md docs/dsh-integration.zh-CN.md docs/dsh-validatio
18
18
  recursive-include docs/adr *.md
19
19
 
20
20
  recursive-include integrations/shared *.md *.json *.yml *.toml
21
+ recursive-include integrations/pi *.mjs *.md
22
+ include integrations/agent-hosts/package.json integrations/agent-hosts/package-lock.json
23
+ include docs/universal-owner-status.md docs/universal-owner-status.zh-CN.md
24
+ recursive-include docs/releases *.md
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: qdrant-memory-mcp
3
- Version: 0.2.2
3
+ Version: 0.2.4
4
4
  Summary: Metadata-only stdio MCP distribution of the Qdrant Memory Runtime
5
5
  License-Expression: MIT
6
6
  Project-URL: Homepage, https://github.com/cnkang/qdrant-memory-mcp
@@ -15,16 +15,16 @@ Classifier: Operating System :: OS Independent
15
15
  Requires-Python: >=3.11
16
16
  Description-Content-Type: text/markdown
17
17
  License-File: LICENSE
18
- Requires-Dist: hermes-plugin-qdrant-memory[mcp]==0.4.0
18
+ Requires-Dist: hermes-plugin-qdrant-memory[mcp]==0.5.0
19
19
  Dynamic: license-file
20
20
 
21
21
  # Qdrant Memory MCP
22
22
 
23
- For shared production deployments, read the [deployment security guide](docs/shared-deployment-security.md). Owner-only database write credentials are required independently of MCP grants. Destination protection and shared doctor are unpublished Runtime additions; published pins and installation commands remain unchanged.
23
+ For shared production deployments, read the [deployment security guide](docs/shared-deployment-security.md). Owner-only database write credentials are required independently of MCP grants. Runtime 0.5.0 includes destination protection and shared doctor; the operator must configure these controls. See the [Owner support record](docs/universal-owner-status.md) for support limits.
24
24
 
25
25
  ## One Memory, Multiple Agents — opt-in shared owner
26
26
 
27
- The distribution adds an opt-in single-owner service and stdio bridge. Install Runtime 0.4.0 to use them. See [shared integration guide](integrations/shared/README.md). Private defaults are unchanged. Native Provider automatic shared extraction is deferred.
27
+ The distribution adds an opt-in single-owner service and stdio bridge. Install Runtime 0.5.0 to use them. See [shared integration guide](integrations/shared/README.md). Private defaults are unchanged. Native Provider automatic shared extraction is deferred.
28
28
 
29
29
  <!-- mcp-name: io.github.cnkang/qdrant-memory -->
30
30
 
@@ -38,14 +38,14 @@ Persistent, scoped memory for AI agents through four explicit **stdio MCP** tool
38
38
  This repository distributes the existing [Python Runtime](https://github.com/cnkang/hermes-plugin-qdrant-memory).
39
39
  Its metadata-only wheel contains no Python business implementation. The console
40
40
  script points directly to `qdrant_memory.standalone:main` and depends on
41
- `hermes-plugin-qdrant-memory[mcp]==0.4.0`.
41
+ `hermes-plugin-qdrant-memory[mcp]==0.5.0`.
42
42
 
43
- See [0.1.4 release notes](docs/releases/0.1.4.md) for WorkBuddy assets, SDK compatibility and upgrade guidance.
43
+ See [0.2.4 release notes](docs/releases/0.2.4.md) for source alignment, WorkBuddy assets and compatibility boundaries.
44
44
 
45
45
  Before using an exact-version installation command, confirm that version on
46
- the [PyPI release page](https://pypi.org/project/qdrant-memory-mcp/0.2.2/).
46
+ the [PyPI release page](https://pypi.org/project/qdrant-memory-mcp/0.2.4/).
47
47
 
48
- **Versions:** MCP distribution 0.2.2 pins Runtime 0.4.0, which supports MCP
48
+ **Versions:** MCP distribution 0.2.4 pins Runtime 0.5.0, which supports MCP
49
49
  Python SDK 1.x and 2.x (`mcp>=1.30,<3`). The four scoped tools and stdio
50
50
  launch arguments are the same for both SDK majors. It retains the fix for explicit
51
51
  writes of distinct, highly similar texts without an LLM. The commands below use
@@ -92,13 +92,13 @@ Create an operator-owned profile directory and save `qdrant-memory.json` inside:
92
92
  Initialize, then launch (replace `/path/to/profile` with your absolute path):
93
93
 
94
94
  ```bash
95
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home /path/to/profile init
96
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home /path/to/profile mcp
95
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home /path/to/profile init
96
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home /path/to/profile mcp
97
97
  ```
98
98
 
99
99
  The command without `--home` uses `~/.qdrant-memory`, independent of Hermes.
100
100
  Configure and initialize that directory before letting a Registry client launch
101
- `uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp mcp`.
101
+ `uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp mcp`.
102
102
  The executable name matches the package name.
103
103
  The Registry's positional `mcp` selects protocol mode. Its optional named
104
104
  `--home` precedes `mcp` when a client supplies a custom profile.
@@ -107,7 +107,7 @@ Alternatively:
107
107
 
108
108
  ```bash
109
109
  python3 -m venv .venv
110
- .venv/bin/python -m pip install qdrant-memory-mcp==0.2.2
110
+ .venv/bin/python -m pip install qdrant-memory-mcp==0.2.4
111
111
  .venv/bin/qdrant-memory-mcp --home /path/to/profile init
112
112
  .venv/bin/qdrant-memory-mcp --home /path/to/profile mcp
113
113
  ```
@@ -129,7 +129,7 @@ Codex `config.toml` example:
129
129
  ```toml
130
130
  [mcp_servers.qdrant_memory]
131
131
  command = "uvx"
132
- args = ["--from", "qdrant-memory-mcp==0.2.2", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"]
132
+ args = ["--from", "qdrant-memory-mcp==0.2.4", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"]
133
133
  ```
134
134
 
135
135
  OpenCode `opencode.json` example:
@@ -140,7 +140,7 @@ OpenCode `opencode.json` example:
140
140
  "mcp": {
141
141
  "qdrant_memory": {
142
142
  "type": "local",
143
- "command": ["uvx", "--from", "qdrant-memory-mcp==0.2.2", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"],
143
+ "command": ["uvx", "--from", "qdrant-memory-mcp==0.2.4", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"],
144
144
  "enabled": true
145
145
  }
146
146
  }
@@ -204,10 +204,9 @@ the optional [Skill](https://github.com/cnkang/skills/tree/main/qdrant-memory).
204
204
 
205
205
  Use the [WorkBuddy connector](integrations/workbuddy/README.md) or the
206
206
  [DSH installation guide](docs/dsh-integration.md) for explicit durable memory.
207
- Both reuse the Python Runtime, the four MCP tools and the canonical Skill. The
208
- published [managed launcher](integrations/managed/README.md) prepares private
209
- Python and CPU-model dependencies with Node.js, so the managed routes do not
210
- require a system Python, uvx or Ollama installation. The DSH Bundle is
207
+ Both reuse the Python Runtime, the four MCP tools and the canonical Skill. The published [managed launcher](integrations/managed/README.md) prepares private Python
208
+ and CPU-model dependencies with Node.js. Thus, the managed routes do not require a
209
+ system Python, uvx or Ollama installation. The DSH Bundle is
211
210
  distributed as `@cnkang/qdrant-memory-dsh-bundle`. Existing Hermes profiles
212
211
  and defaults are unchanged. See [architecture and version matrix](docs/cross-harness-architecture.md)
213
212
  and [validation limits](docs/dsh-validation.md).
@@ -1,10 +1,10 @@
1
1
  # Qdrant Memory MCP
2
2
 
3
- For shared production deployments, read the [deployment security guide](docs/shared-deployment-security.md). Owner-only database write credentials are required independently of MCP grants. Destination protection and shared doctor are unpublished Runtime additions; published pins and installation commands remain unchanged.
3
+ For shared production deployments, read the [deployment security guide](docs/shared-deployment-security.md). Owner-only database write credentials are required independently of MCP grants. Runtime 0.5.0 includes destination protection and shared doctor; the operator must configure these controls. See the [Owner support record](docs/universal-owner-status.md) for support limits.
4
4
 
5
5
  ## One Memory, Multiple Agents — opt-in shared owner
6
6
 
7
- The distribution adds an opt-in single-owner service and stdio bridge. Install Runtime 0.4.0 to use them. See [shared integration guide](integrations/shared/README.md). Private defaults are unchanged. Native Provider automatic shared extraction is deferred.
7
+ The distribution adds an opt-in single-owner service and stdio bridge. Install Runtime 0.5.0 to use them. See [shared integration guide](integrations/shared/README.md). Private defaults are unchanged. Native Provider automatic shared extraction is deferred.
8
8
 
9
9
  <!-- mcp-name: io.github.cnkang/qdrant-memory -->
10
10
 
@@ -18,14 +18,14 @@ Persistent, scoped memory for AI agents through four explicit **stdio MCP** tool
18
18
  This repository distributes the existing [Python Runtime](https://github.com/cnkang/hermes-plugin-qdrant-memory).
19
19
  Its metadata-only wheel contains no Python business implementation. The console
20
20
  script points directly to `qdrant_memory.standalone:main` and depends on
21
- `hermes-plugin-qdrant-memory[mcp]==0.4.0`.
21
+ `hermes-plugin-qdrant-memory[mcp]==0.5.0`.
22
22
 
23
- See [0.1.4 release notes](docs/releases/0.1.4.md) for WorkBuddy assets, SDK compatibility and upgrade guidance.
23
+ See [0.2.4 release notes](docs/releases/0.2.4.md) for source alignment, WorkBuddy assets and compatibility boundaries.
24
24
 
25
25
  Before using an exact-version installation command, confirm that version on
26
- the [PyPI release page](https://pypi.org/project/qdrant-memory-mcp/0.2.2/).
26
+ the [PyPI release page](https://pypi.org/project/qdrant-memory-mcp/0.2.4/).
27
27
 
28
- **Versions:** MCP distribution 0.2.2 pins Runtime 0.4.0, which supports MCP
28
+ **Versions:** MCP distribution 0.2.4 pins Runtime 0.5.0, which supports MCP
29
29
  Python SDK 1.x and 2.x (`mcp>=1.30,<3`). The four scoped tools and stdio
30
30
  launch arguments are the same for both SDK majors. It retains the fix for explicit
31
31
  writes of distinct, highly similar texts without an LLM. The commands below use
@@ -72,13 +72,13 @@ Create an operator-owned profile directory and save `qdrant-memory.json` inside:
72
72
  Initialize, then launch (replace `/path/to/profile` with your absolute path):
73
73
 
74
74
  ```bash
75
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home /path/to/profile init
76
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home /path/to/profile mcp
75
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home /path/to/profile init
76
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home /path/to/profile mcp
77
77
  ```
78
78
 
79
79
  The command without `--home` uses `~/.qdrant-memory`, independent of Hermes.
80
80
  Configure and initialize that directory before letting a Registry client launch
81
- `uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp mcp`.
81
+ `uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp mcp`.
82
82
  The executable name matches the package name.
83
83
  The Registry's positional `mcp` selects protocol mode. Its optional named
84
84
  `--home` precedes `mcp` when a client supplies a custom profile.
@@ -87,7 +87,7 @@ Alternatively:
87
87
 
88
88
  ```bash
89
89
  python3 -m venv .venv
90
- .venv/bin/python -m pip install qdrant-memory-mcp==0.2.2
90
+ .venv/bin/python -m pip install qdrant-memory-mcp==0.2.4
91
91
  .venv/bin/qdrant-memory-mcp --home /path/to/profile init
92
92
  .venv/bin/qdrant-memory-mcp --home /path/to/profile mcp
93
93
  ```
@@ -109,7 +109,7 @@ Codex `config.toml` example:
109
109
  ```toml
110
110
  [mcp_servers.qdrant_memory]
111
111
  command = "uvx"
112
- args = ["--from", "qdrant-memory-mcp==0.2.2", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"]
112
+ args = ["--from", "qdrant-memory-mcp==0.2.4", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"]
113
113
  ```
114
114
 
115
115
  OpenCode `opencode.json` example:
@@ -120,7 +120,7 @@ OpenCode `opencode.json` example:
120
120
  "mcp": {
121
121
  "qdrant_memory": {
122
122
  "type": "local",
123
- "command": ["uvx", "--from", "qdrant-memory-mcp==0.2.2", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"],
123
+ "command": ["uvx", "--from", "qdrant-memory-mcp==0.2.4", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"],
124
124
  "enabled": true
125
125
  }
126
126
  }
@@ -184,10 +184,9 @@ the optional [Skill](https://github.com/cnkang/skills/tree/main/qdrant-memory).
184
184
 
185
185
  Use the [WorkBuddy connector](integrations/workbuddy/README.md) or the
186
186
  [DSH installation guide](docs/dsh-integration.md) for explicit durable memory.
187
- Both reuse the Python Runtime, the four MCP tools and the canonical Skill. The
188
- published [managed launcher](integrations/managed/README.md) prepares private
189
- Python and CPU-model dependencies with Node.js, so the managed routes do not
190
- require a system Python, uvx or Ollama installation. The DSH Bundle is
187
+ Both reuse the Python Runtime, the four MCP tools and the canonical Skill. The published [managed launcher](integrations/managed/README.md) prepares private Python
188
+ and CPU-model dependencies with Node.js. Thus, the managed routes do not require a
189
+ system Python, uvx or Ollama installation. The DSH Bundle is
191
190
  distributed as `@cnkang/qdrant-memory-dsh-bundle`. Existing Hermes profiles
192
191
  and defaults are unchanged. See [architecture and version matrix](docs/cross-harness-architecture.md)
193
192
  and [validation limits](docs/dsh-validation.md).
@@ -1,23 +1,23 @@
1
1
  # Qdrant Memory MCP
2
2
 
3
- 共享生产部署请参阅[部署安全指南](docs/shared-deployment-security.md)。Agent 只应接收 Owner 客户端令牌,不应接收 Qdrant 写凭据。本地锁无法阻止远程数据库写入。新保护策略和诊断尚未发布;分发版本、依赖固定值和安装命令保持不变。
3
+ 共享生产部署请参阅[部署安全指南](docs/shared-deployment-security.md)。Owner 必须独占数据库应用写凭据,MCP 授权不能替代此要求。Runtime 0.5.0 已包含目的地保护和 shared doctor,须由操作者配置这些控制。支持边界请查看 [Owner 支持记录](docs/universal-owner-status.zh-CN.md)。
4
4
 
5
5
  ## One Memory, Multiple Agents — 可选启用的共享 owner
6
6
 
7
- 本分发新增显式启用的单 owner 共享服务和 stdio 桥接,需安装 Runtime 0.4.0。见[共享接入指南](integrations/shared/README.md)。私有默认配置与 DSH/WorkBuddy 托管配置不变;Hermes Native Provider 自动共享提取尚未实现。
7
+ 本分发新增显式启用的单 owner 共享服务和 stdio 桥接,需安装 Runtime 0.5.0。见[共享接入指南](integrations/shared/README.md)。私有默认配置与 DSH/WorkBuddy 托管配置不变;Hermes Native Provider 自动共享提取尚未实现。
8
8
 
9
9
  这是 Qdrant Memory 的独立 PyPI 包装与 MCP Registry 分发仓库。
10
10
  所有业务逻辑来自唯一的 [Python Runtime](https://github.com/cnkang/hermes-plugin-qdrant-memory),
11
11
  本仓库不复制 Runtime 或 [Agent Skill](https://github.com/cnkang/skills/tree/main/qdrant-memory)。
12
12
  `qdrant-memory-mcp` 直接引用 `qdrant_memory.standalone:main`,固定依赖
13
- `hermes-plugin-qdrant-memory[mcp]==0.4.0`,不需要安装 Hermes。
13
+ `hermes-plugin-qdrant-memory[mcp]==0.5.0`,不需要安装 Hermes。
14
14
 
15
- WorkBuddy 资产、SDK 兼容性和升级指引见 [0.1.4 发布说明](docs/releases/0.1.4.zh-CN.md)。
15
+ 源码对齐、WorkBuddy 资产和兼容边界见 [0.2.4 发布说明](docs/releases/0.2.4.zh-CN.md)。
16
16
 
17
- 使用固定版本安装命令前,请在 [PyPI 版本页面](https://pypi.org/project/qdrant-memory-mcp/0.2.2/)
17
+ 使用固定版本安装命令前,请在 [PyPI 版本页面](https://pypi.org/project/qdrant-memory-mcp/0.2.4/)
18
18
  确认该版本已公开发布。
19
19
 
20
- **版本:** 分发 0.2.2 固定依赖 Runtime 0.4.0,支持 MCP Python SDK 1.x 和 2.x
20
+ **版本:** 分发 0.2.4 固定依赖 Runtime 0.5.0,支持 MCP Python SDK 1.x 和 2.x
21
21
  (`mcp>=1.30,<3`);四个固定作用域工具和 stdio 启动参数保持一致。
22
22
  保留不同但高度相似文本的显式写入修复,
23
23
  无需 LLM。下文安装命令使用这些精确版本。发行产物见
@@ -31,9 +31,11 @@ Skill 仅提供可选指导,不是运行依赖。Hermes 的自动提取和 pre
31
31
  最少步骤见 [本地 Ollama 快速开始](docs/quickstart.zh-CN.md),包括复用已有模型、
32
32
  缺少模型时的安装指引、独立 WorkBuddy profile、连接配置和首次保存/搜索验证。
33
33
  这条本地路径不需要 Qdrant Server、Docker、云账号或 Embedding API Key;
34
- 本直接路径仍需要准备 Python/uv,并完成一次 profile 配置。
34
+ 本直接路径仍需要准备 Python/uv,并完成一次 profile 配置。受管的 WorkBuddy
35
+ 连接器和 DSH Bundle 则由 Node.js 准备这些依赖。
35
36
 
36
- 需要 Python 3.11+。用户必须自行配置 Qdrant 与 Embedding。
37
+ 需要 Python 3.11+,以及 [uv](https://docs.astral.sh/uv/) 或 Python 虚拟环境。
38
+ 必须自行配置存储和 Embedding 服务。
37
39
  在可信 profile 目录内创建 `qdrant-memory.json`:
38
40
 
39
41
  ```json
@@ -51,12 +53,12 @@ Skill 仅提供可选指导,不是运行依赖。Hermes 的自动提取和 pre
51
53
  示例要求自己启动 Ollama 并安装对应模型。将路径替换为自己的绝对路径:
52
54
 
53
55
  ```bash
54
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home /path/to/profile init
55
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home /path/to/profile mcp
56
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home /path/to/profile init
57
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home /path/to/profile mcp
56
58
  ```
57
59
 
58
60
  省略 `--home` 时使用 `~/.qdrant-memory`,与 Hermes profile 独立。
59
- Registry 默认运行 `uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp mcp`,
61
+ Registry 默认运行 `uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp mcp`,
60
62
  应先配置、初始化默认目录。
61
63
  客户端可通过 `mcp` 前面的可选 `--home` 参数选择自定义 profile。
62
64
 
@@ -64,7 +66,7 @@ Registry 默认运行 `uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp mcp
64
66
 
65
67
  ```bash
66
68
  python3 -m venv .venv
67
- .venv/bin/python -m pip install qdrant-memory-mcp==0.2.2
69
+ .venv/bin/python -m pip install qdrant-memory-mcp==0.2.4
68
70
  .venv/bin/qdrant-memory-mcp --home /path/to/profile init
69
71
  .venv/bin/qdrant-memory-mcp --home /path/to/profile mcp
70
72
  ```
@@ -82,7 +84,7 @@ Codex `config.toml`:
82
84
  ```toml
83
85
  [mcp_servers.qdrant_memory]
84
86
  command = "uvx"
85
- args = ["--from", "qdrant-memory-mcp==0.2.2", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"]
87
+ args = ["--from", "qdrant-memory-mcp==0.2.4", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"]
86
88
  ```
87
89
 
88
90
  OpenCode `opencode.json`:
@@ -93,7 +95,7 @@ OpenCode `opencode.json`:
93
95
  "mcp": {
94
96
  "qdrant_memory": {
95
97
  "type": "local",
96
- "command": ["uvx", "--from", "qdrant-memory-mcp==0.2.2", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"],
98
+ "command": ["uvx", "--from", "qdrant-memory-mcp==0.2.4", "qdrant-memory-mcp", "--home", "/path/to/profile", "mcp"],
97
99
  "enabled": true
98
100
  }
99
101
  }
@@ -103,6 +105,8 @@ OpenCode `opencode.json`:
103
105
  Pi 需要另外安装 MCP 客户端扩展;将上述 command/args 填入该扩展支持的配置。
104
106
  本仓库不声称 Pi 内置 MCP,也不声称通用扩展配置格式。
105
107
  这些是配置示例;分发测试使用官方 Python MCP SDK,不把未实测的 Agent 应用列为已验证。
108
+ 各客户端的实证范围与限制见 Runtime 的
109
+ [客户端证据与限制](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/docs/mcp.md)。
106
110
 
107
111
  ## 工具、安全与限制
108
112
 
@@ -135,8 +139,10 @@ CI 对 Linux/macOS/Windows、Python 3.11/3.14 的 wheel/sdist 安装运行真实
135
139
 
136
140
  CI 优先使用正式 PyPI Runtime。新 Runtime 发布前,CI 使用 `runtime-source.json` 固定的不可变修订
137
141
  构建本地 wheel;正式包元数据始终依赖固定 PyPI 版本,发布流程禁止这种回退。
138
- 详见 [英文说明](README.md)、[发布清单](docs/publishing.md) 与
139
- [Runtime 验证](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/docs/validation.md)。
142
+ 详见 [CI 与依赖维护](docs/ci.md)、[发布清单](docs/publishing.md)、
143
+ [架构](docs/architecture.md) 与
144
+ [Runtime 验证](https://github.com/cnkang/hermes-plugin-qdrant-memory/blob/main/docs/validation.md),
145
+ 以及可选的 [Skill](https://github.com/cnkang/skills/tree/main/qdrant-memory)。
140
146
 
141
147
  ## WorkBuddy 与 DeepSeek Harness
142
148
 
@@ -0,0 +1,87 @@
1
+ # GitHub checks and dependency maintenance
2
+
3
+ Distribution CI tests the released Runtime version in fresh wheel and sdist environments.
4
+ It rejects skipped acceptance tests.
5
+ The separate `owner-lifecycle` job runs the Hermes-to-Pi source preview test.
6
+ This job installs fixed Runtime, Hermes, and Pi versions.
7
+
8
+ It also rejects skipped tests.
9
+ Distribution CI excludes this test because Runtime 0.4.0 does not provide the preview API.
10
+ An unavailable preview must not weaken distribution checks.
11
+
12
+ - Distribution CI builds metadata-only artifacts.
13
+ It tests installed MCP behavior on Linux, macOS, and Windows.
14
+ Tests cover Python 3.11 and 3.14 with MCP Python SDK 1.x and 2.x.
15
+ Publication also tests both SDK versions against wheel and sdist installations with the public Runtime release.
16
+ The protected branch requires all 12 operating system, Python, and SDK combinations.
17
+ - Cross-harness integration runs the official DSH client with a temporary profile.
18
+ It installs the packed Bundle through the real `dsh plugin` command.
19
+ It runs the exact public `npx` launcher commands on Linux, macOS, and Windows.
20
+ Tests cover the initial handshake, preparation, memory operations, and persistence.
21
+ - Repository quality runs Ruff on release scripts and tests.
22
+ It runs actionlint on every workflow, including shell steps.
23
+ CI verifies the SHA256 digest of the actionlint archive.
24
+ - CodeQL analyzes Python and GitHub Actions with `security-extended` queries
25
+ on PRs, main pushes and every Monday. The paired init/analyze actions use the
26
+ same immutable commit.
27
+ - Dependency review blocks PRs that introduce high or critical dependency
28
+ vulnerabilities. It uses read-only access and does not post PR comments.
29
+ - Dependabot checks pip manifests and GitHub Actions each Monday at 09:00
30
+ Asia/Singapore, grouping updates by ecosystem. Updates remain reviewed PRs.
31
+ There is no automatic merge or publication.
32
+
33
+ Actions use immutable commit pins. Dependabot updates both occurrences of the
34
+ CodeQL action together. The repository enables Dependabot security updates, secret scanning,
35
+ and push protection. These checks require no additional service token.
36
+
37
+ ## DSH dependency security and update channels
38
+
39
+ The reproducible cross-harness gate pins official DSH packages at
40
+ `0.2.1-rc.2`. A temporary test-only override pins MCP Client to `2.3.0`, with Core `2.3.0`.
41
+ It fixes [cross-origin redirect leakage](https://github.com/advisories/GHSA-6prh-2h8m-c8cw).
42
+ The earlier [OAuth fix](https://github.com/advisories/GHSA-6qxp-vccf-f47h) remains included.
43
+ Remove the override after an upstream DSH update uses a fixed client, then rerun the actual client acceptance.
44
+ The lockfile test rejects affected versions, including nested copies.
45
+
46
+ The redirect advisory affects HTTP and OAuth. This repository's DSH acceptance uses unaffected stdio.
47
+ GitHub closes the alert only after the corrected lockfile reaches the default branch and is evaluated.
48
+ A feature branch push alone does not close it.
49
+
50
+ The separate `DSH next compatibility` workflow resolves the three official
51
+ packages from `next` weekly, manually, and when relevant integration sources
52
+ change. It runs the same acceptance tests for the real client, CLI, and Bundle.
53
+ It rejects skipped tests and high or critical advisories.
54
+ It retains the resolved dependency tree, generated lockfile, and audit report.
55
+ These results show compatibility. Release checks still use exact package versions.
56
+
57
+ To adopt a tested `next` version, update all three version pins.
58
+ Update the committed lockfile.
59
+ Keep `npm ci` in release checks.
60
+ Do not use floating package versions for these checks.
61
+ The upstream packages do not synchronize their npm `latest` tags.
62
+
63
+ The `next` probe retains the test-only overrides.
64
+ Inspect its resolved tree before removing an override.
65
+
66
+ A second test-only override selects `fflate 0.8.3` for `@deepseek-ai/libreoffice-kit`.
67
+ It fixes the [malformed ZIP64 parser advisory](https://github.com/advisories/GHSA-px8p-9vwx-vf98).
68
+ The three official DSH packages stay at `0.2.1-rc.2`.
69
+ Remove this override after an upstream Office dependency uses a fixed parser.
70
+ Then repeat the clean installation, audit, and actual DSH acceptance tests.
71
+ Do not use `npm audit fix --force`.
72
+
73
+ The clean installation and `npm audit` on 2026-10-20 (UTC) reported zero vulnerabilities.
74
+ The lockfile test rejects affected parser copies, including nested copies.
75
+ Acceptance tests resolve the parser through the Office package.
76
+ They verify a ZIP roundtrip and reject a malformed ZIP64 archive within a fixed timeout.
77
+ These npm dependencies serve development tests only.
78
+ Python artifacts and the configuration-only Bundle do not include them.
79
+
80
+ The Runtime dependency uses the exact version `0.4.0`.
81
+ For a Runtime update, also update compatibility expectations and the preparation fixture.
82
+ A dependency-only PR cannot bypass distribution metadata and protocol checks.
83
+ This repository scans distribution scripts and workflows.
84
+ The upstream Runtime repository scans Runtime business code.
85
+
86
+ Publication requires a tag, the existing protected environments, and explicit confirmation.
87
+ New checks do not trigger a release.
@@ -16,7 +16,7 @@ uses) and no system Python, uvx, Ollama or Qdrant Server. Prepare the shared
16
16
  backend first:
17
17
 
18
18
  ```sh
19
- npx -y @cnkang/qdrant-memory-launcher@0.1.0-rc.3 prepare dsh
19
+ npx -y @cnkang/qdrant-memory-launcher@0.1.0-rc.4 prepare dsh
20
20
  ```
21
21
 
22
22
  Wait for `{"ready":true,"host":"dsh"}`. Preparation downloads the private
@@ -52,8 +52,8 @@ at `~/.qdrant-memory-dsh` instead of `~/.qdrant-memory`. Put your chosen scope a
52
52
  embedding settings in that profile's `qdrant-memory.json`, then initialize it:
53
53
 
54
54
  ```sh
55
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home "$HOME/.qdrant-memory-dsh" init
56
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home "$HOME/.qdrant-memory-dsh" doctor
55
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home "$HOME/.qdrant-memory-dsh" init
56
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home "$HOME/.qdrant-memory-dsh" doctor
57
57
  dsh web --patch /absolute/path/to/qdrant-memory-mcp/integrations/dsh/qdrant-memory.cordis.yml
58
58
  ```
59
59
 
@@ -103,10 +103,9 @@ operation. A busy-profile error means another process owns storage. Close that
103
103
  connection normally.
104
104
  Never remove a data lock, reset storage or change a fingerprint to force startup.
105
105
 
106
- To disconnect, remove the Bundle or this launch's overlay, then stop or
107
- restart the profile: a running profile keeps its loaded Bundle set, and only
108
- the stop or restart closes the active MCP process and releases the storage
109
- writer lease. Data stays on disk. Verify persistence by saving a synthetic fact and
106
+ To disconnect, remove the Bundle or the overlay of this launch. Then stop or restart the
107
+ profile. A running profile keeps its loaded Bundle set. Only the stop or the restart
108
+ closes the active MCP process and releases the storage writer lease. Data stays on disk. Verify persistence by saving a synthetic fact and
110
109
  recalling it in a new session without the old transcript. Then update or delete
111
110
  the returned ID and fully restart DSH.
112
111
  Real model/GUI acceptance is separate from the automated official-client suite.
@@ -3,7 +3,7 @@
3
3
  共享部署的 DSH 只应持有独立的 Owner 客户端令牌,数据库写凭据由 Owner 独占。见[部署安全指南](shared-deployment-security.md)。普通托管 Bundle 保持私有模式,不会自动登记共享目的地。
4
4
 
5
5
  通过 DSH 官方 MCP 客户端,可以搜索、保存、更新和删除长期记忆。
6
- 它提供明确的记忆操作,不会自动保存每一轮对话。
6
+ 记忆在新的会话和服务重启后仍然保留。它提供明确的记忆操作,不会自动保存每一轮对话。
7
7
 
8
8
  [English](dsh-integration.md) · [验证范围](dsh-validation.md)
9
9
 
@@ -14,7 +14,7 @@
14
14
  先准备共享后端:
15
15
 
16
16
  ```sh
17
- npx -y @cnkang/qdrant-memory-launcher@0.1.0-rc.3 prepare dsh
17
+ npx -y @cnkang/qdrant-memory-launcher@0.1.0-rc.4 prepare dsh
18
18
  ```
19
19
 
20
20
  等待输出 `{"ready":true,"host":"dsh"}`。准备过程会下载私有 Python 环境、固定版本的
@@ -22,19 +22,19 @@ Runtime wheel 和经过校验的 CPU 嵌入模型,可能需要数分钟并需
22
22
  安装到一个 profile:
23
23
 
24
24
  ```sh
25
- dsh plugin --profile <名称> add @cnkang/qdrant-memory-dsh-bundle
25
+ dsh plugin --profile <name> add @cnkang/qdrant-memory-dsh-bundle
26
26
  ```
27
27
 
28
28
  若所用 npm 镜像尚未同步该包,可改从仓库 Release 下载
29
29
  `cnkang-qdrant-memory-dsh-bundle-0.1.1.tgz`,用文件路径安装。不启动即可先验证层:
30
30
 
31
31
  ```sh
32
- dsh --profile <名称> --dump-config
32
+ dsh --profile <name> --dump-config
33
33
  ```
34
34
 
35
35
  DSH 会先运行临时探测进程,再启动常驻连接。探测进程不会执行安装或下载模型;
36
36
  准备始终是上面的显式步骤。后端就绪前,工具会明确提示没有执行任何操作,
37
- 写入不会被排队。DSH 的数据目录(`<托管根>/profiles/dsh/local`)与 WorkBuddy、
37
+ 写入不会被排队。DSH 的数据目录(`<managed-root>/profiles/dsh/local`)与 WorkBuddy、
38
38
  Hermes 相互独立。更新、卸载与恢复说明见 [Bundle 说明](../integrations/dsh/bundle/README.md)。
39
39
 
40
40
  ## 备选:已发布的 Python/uvx overlay
@@ -45,9 +45,9 @@ Hermes 相互独立。更新、卸载与恢复说明见 [Bundle 说明](../integ
45
45
  然后执行:
46
46
 
47
47
  ```sh
48
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home "$HOME/.qdrant-memory-dsh" init
49
- uvx --from qdrant-memory-mcp==0.2.2 qdrant-memory-mcp --home "$HOME/.qdrant-memory-dsh" doctor
50
- dsh web --patch /绝对路径/qdrant-memory-mcp/integrations/dsh/qdrant-memory.cordis.yml
48
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home "$HOME/.qdrant-memory-dsh" init
49
+ uvx --from qdrant-memory-mcp==0.2.4 qdrant-memory-mcp --home "$HOME/.qdrant-memory-dsh" doctor
50
+ dsh web --patch /absolute/path/to/qdrant-memory-mcp/integrations/dsh/qdrant-memory.cordis.yml
51
51
  ```
52
52
 
53
53
  Windows 请使用对应的绝对路径。启动 DSH 前可用环境变量
@@ -90,3 +90,8 @@ DSH 会清理继承环境中名称包含 KEY、PASSWORD、SECRET、TOKEN 的变
90
90
  验收时在会话 A 保存合成事实,在不传入旧对话的会话 B 检索并使用;再按返回的 ID
91
91
  更新和删除,并完整重启 DSH 验证持久化。自动化官方客户端测试与真实模型/GUI
92
92
  会话验收分别记录,不相互替代。
93
+
94
+ 适配器遵循官方
95
+ [MCP 客户端契约](https://github.com/deepseek-ai/deepseek-harness/blob/master/packages/mcp/mcp-client/README.md)、
96
+ [记忆指南](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/user/guide/mcp-memory.md)
97
+ 和 [Skill 文件系统 provider](https://github.com/deepseek-ai/deepseek-harness/blob/master/packages/skill/skill-filesystem/README.md)。
@@ -14,17 +14,29 @@ The official `next` release [0.2.1-rc.2](https://github.com/deepseek-ai/deepseek
14
14
  passed all three real local acceptance tests: MCP Client lifecycle/CRUD/restart,
15
15
  CLI overlay preservation, and packed Bundle installation/composition/removal.
16
16
  The CLI, MCP Client and filesystem Skill provider are pinned together at that
17
- version. MCP Client/Core resolve to the OAuth advisory fix `2.2.0`.
18
- The Bundle peer range retains the old RC line and explicitly admits the new RC
19
- line, because npm prerelease matching does not infer it from the old range.
17
+ version. The original validation used the OAuth advisory fix `2.2.0`.
18
+ The Bundle peer range retains the old RC line and explicitly admits the new RC line.
19
+ The old range does not include the new npm prerelease line.
20
+
20
21
  The Desktop GUI evidence below remains for 0.2.0-rc.2. This update does not claim
21
22
  new GUI acceptance. The independent floating `next` CI probe complements the
22
23
  committed exact-version release gate. See [dependency maintenance](ci.md).
24
+
23
25
  The updated distribution suite passed 141 tests. Ruff, actionlint, clean npm
24
26
  installation, wheel/sdist builds and strict metadata checks also passed locally.
25
27
 
26
28
  ## Local automated coverage
27
29
 
30
+ The current test lock uses a temporary MCP Client `2.3.0` override for the cross-origin redirect fix.
31
+ Core also resolves to `2.3.0`. The three official DSH packages remain at `0.2.1-rc.2`.
32
+ The override affects development tests. It does not add dependencies to the configuration-only Bundle.
33
+
34
+ A separate Office dependency override selects `fflate 0.8.3` for `@deepseek-ai/libreoffice-kit`.
35
+ Clean installation and `npm audit` reported zero vulnerabilities on 2026-10-20 (UTC).
36
+ The Office parser passed a ZIP roundtrip with Unicode text and binary data.
37
+ It also rejected a malformed ZIP64 archive within the test timeout.
38
+ See [dependency maintenance](ci.md) for the advisory and removal condition.
39
+
28
40
  | Layer | Verified behavior |
29
41
  | --- | --- |
30
42
  | Existing Python MCP | Four schemas, CRUD, fixed scope, WriterLease, redaction, restart/recovery and protocol-only stdout |
@@ -52,6 +64,7 @@ The subsequent fresh-root run that interrupted/resumed installation completed in
52
64
  DSH client tests use the official package and real stdio processes. A fixture
53
65
  tool registry provides an observation seam. Those tests do not exercise the
54
66
  whole AgentLoop or every permission policy. Pre-cancellation is tested.
67
+
55
68
  Cancellation of a dispatched durable write can have an uncertain outcome. The
56
69
  caller must check the exact operation and its ID before any repeat. Do not
57
70
  repeat an uncertain write unless a repeat is safe for that operation. No write replay is added by the adapter.
@@ -79,11 +92,13 @@ WorkBuddy 5.8.2 connected a custom managed-launcher source entry, discovered all
79
92
  four tools and created an isolated WorkBuddy profile automatically. Its actual
80
93
  model saved and searched Chinese/English synthetic facts. A fresh conversation,
81
94
  without the earlier transcript, retrieved the facts and used them to answer the
82
- requested weekdays. Full WorkBuddy quit released the launcher process. After
83
- relaunch, preparation was explicitly repaired/reconnected during a dependency
95
+ requested weekdays. Full WorkBuddy quit released the launcher process.
96
+
97
+ After relaunch, preparation was explicitly repaired/reconnected during a dependency
84
98
  environment change. Actual GUI searches confirmed the same records and IDs.
85
99
  Exact-ID update/delete and subsequent searches then passed. This is a
86
100
  restart/recovery result, not an uninterrupted cold-install UX certification.
101
+
87
102
  The GUI used an explicitly selected existing Node executable
88
103
  and shared pre-provisioned program/model files. This is not marketplace ZIP
89
104
  import, managed-Node provisioning or a clean-machine one-click certification.
@@ -93,9 +108,11 @@ through its Plugin Manager and activated the official MCP client. The actual
93
108
  model saved/searched two synthetic facts. A fresh session retrieved and used
94
109
  them without the previous transcript. Exact-ID update preserved the first ID,
95
110
  and exact-ID deletion removed the second from subsequent search. After a verified
96
- full desktop exit, backend diagnostics could reopen storage successfully. After
97
- relaunch, a new session loaded the canonical Skill through DSH's standard Skill
111
+ full desktop exit, backend diagnostics could reopen storage successfully.
112
+
113
+ After relaunch, a new session loaded the canonical Skill through DSH's standard Skill
98
114
  tool, recalled the updated record and continued to exclude the deleted ID.
115
+
99
116
  The test used
100
117
  the prepared CPU Runtime and a dedicated DSH profile. No DSH core changes were
101
118
  needed. Remaining desktop lifecycle and platform cases are separate release gates.
@@ -129,11 +146,11 @@ workflow refuses unpublished pins. The Runtime wheel is public on PyPI. The
129
146
  MCP distribution `v0.1.4` is published on PyPI and the MCP Registry, and its
130
147
  GitHub Release carries the connector assets (2026-10-16). The DSH Bundle
131
148
  0.1.1 is published on npm (2026-10-18), and its GitHub Release carries the
132
- tagged tgz and checksum. Marketplace listing review, managed Node GUI
133
- import in WorkBuddy, full application restart on a clean machine, forced
134
- installer-crash recovery, dispatch-time cancellation, every HMR/profile-switch
135
- case, and production upgrade/rollback remain separate release gates. Cloud
136
- multi-writer sharing and automatic DSH extraction/prefetch are not implemented.
149
+ tagged tgz and checksum.
150
+
151
+ The remaining gates include marketplace review, import with managed Node in WorkBuddy, and a full restart on a clean machine.
152
+ They also include installer-crash recovery, dispatch-time cancellation, HMR/profile-switch cases, and production upgrade or rollback.
153
+ Cloud multi-writer sharing and automatic DSH extraction/prefetch are not implemented.
137
154
 
138
155
  Keep one active owner for embedded storage. Do not bypass locks or reuse Hermes
139
156
  profiles implicitly. See [Hermes compatibility](hermes-compatibility.md),
@@ -1,4 +1,4 @@
1
- # 0.2.2 publication checklist
1
+ # 0.2.4 publication checklist
2
2
 
3
3
  [English](publishing.md) | [简体中文](publishing.zh-CN.md)
4
4
 
@@ -12,7 +12,7 @@ An example identifies the intended release. It does not prove public availabilit
12
12
  Verify the exact public version before using its installation command. Announce
13
13
  the release as available only after the checks below confirm both public endpoints.
14
14
 
15
- 1. Verify the existing public Runtime 0.4.0 release and exact dependency.
15
+ 1. Verify the existing public Runtime 0.5.0 release and exact dependency.
16
16
  Do not recreate its tag or publish it again for this distribution.
17
17
  2. Recheck existing PyPI Trusted Publishers (PyPI account step):
18
18
  - `hermes-plugin-qdrant-memory`: owner `cnkang`, repository
@@ -21,14 +21,14 @@ the release as available only after the checks below confirm both public endpoin
21
21
  workflow `publish.yml`, environment `pypi`.
22
22
  3. Approve protected GitHub environments when prompted. A version tag must point
23
23
  to a main-branch commit and match package metadata. Releases cannot overwrite
24
- an existing version. Reuse the verified public Runtime 0.4.0 artifacts.
24
+ an existing version. Reuse the verified public Runtime 0.5.0 artifacts.
25
25
  4. Run distribution acceptance in public dependency mode. Build/test wheel and
26
26
  sdist from a new environment using only the exact Runtime PyPI release.
27
- 5. Create distribution tag v0.2.2 after confirmation. Its workflow builds and
27
+ 5. Create distribution tag v0.2.4 after confirmation. Its workflow builds and
28
28
  tests before protected PyPI publication, verifies public metadata, validates
29
29
  with the official publisher, then uses `github-oidc` for Registry publication.
30
30
  6. Verify PyPI ownership marker and the public Registry entry
31
- `io.github.cnkang/qdrant-memory` version 0.2.2. Publish the release announcement
31
+ `io.github.cnkang/qdrant-memory` version 0.2.4. Publish the release announcement
32
32
  only after the public endpoints and public-install acceptance confirm the release.
33
33
 
34
34
  The distribution workflow has a tag-only manual `registry_only` retry mode.