test: cover qdrant delete-kinds scoping

.superpowers/sdd/2026-08-08-internal-qdrant-ollama/task-6-report.md

@@ -112,3 +112,33 @@ Notes:
 
 - Legacy HTTP/vector-rest deployments do not gain a new destructive RPC surface from this fix; they keep their previous behavior and continue to fail closed for unsupported cleanup.
 - The broader suite still emits the same pre-existing deprecation and serializer warnings already noted above; this round did not introduce new warnings.
+
+## Fix round 3 (2026-08-08)
+
+Scope:
+
+- Added an adapter-level Qdrant regression for mixed semantic kinds within one workspace plus a second workspace memory point.
+- Verified that `delete_kinds("memory", ["memory"])` emits the real adapter filter with both `workspace_id=demo` and `record_kind=memory`.
+- Verified that non-memory semantic kinds in the same workspace and memory from another workspace survive the delete.
+
+RED evidence:
+
+- Re-review identified a test gap rather than a confirmed runtime bug:
+  - existing coverage asserted only the CLI mock call shape for qdrant memory clear
+  - there was no adapter-level regression proving the real Qdrant delete filter and resulting fake-Qdrant state across mixed semantic kinds/workspaces
+- Added regression:
+  - `tests/test_qdrant_vector_store.py::test_delete_kinds_is_workspace_scoped_and_preserves_other_semantic_kinds`
+
+GREEN evidence:
+
+- Requested focused suite:
+  - `cd harness && .venv/bin/pytest tests/test_qdrant_vector_store.py tests/test_qdrant_cli_commands.py tests/test_semantic_kind_isolation.py -q`
+  - Result: `18 passed`
+- Ruff on changed files:
+  - `cd harness && .venv/bin/ruff check tests/test_qdrant_vector_store.py`
+  - Result: clean
+
+Notes:
+
+- This round required no production change; the new adapter regression passed against the existing Qdrant implementation.
+- The focused suite still emits the same pre-existing `testcontainers.postgres` deprecation warning from `tests/conftest.py`; no new warnings were introduced.