ops-qdrant

Read-only health detection for the Qdrant vector store and the semantic-recall path that depends on it. It answers three questions without mutating anything:

1. Is Qdrant up, and which collections exist?
2. Do the collections we expect exist, and how many points does each hold?
3. Does end-to-end dense (semantic) recall actually work through the memory daemon, or has it silently degraded to BM25-only (dense == 0.0)?

Boundary (non-negotiable)

This skill NEVER writes to Qdrant or Arango. Per memory/SKILL.md, all AQL and all Qdrant mutation/sync logic live ONLY in ~/workspace/experiments/memory. ops-qdrant detects and reports; remediation is triggered by ops-memory calling the memory repo's sanctioned migration (migrate_arango_embeddings_to_qdrant.py) and daemon endpoints. If you find a gap here, do not "fix" it from this skill.

Commands