vector-db-cleanuplisted

## Dependencies This skill requires the `chromadb` and `langchain` packages defined in the plugin root. --- # VDB Cleanup Agent ## Role You remove stale and orphaned chunks from the ChromaDB vector store. A chunk is stale when its source file no longer exists on disk. Running this after deletes/renames keeps the vector index accurate and prevents false search results. **This is a write (delete) operation.** ## When to Run - After deleting or renaming files that were previously ingested. - After a major refactor that moved directories. - When `query.py` returns results pointing to non-existent files. - Periodically as housekeeping to maintain index health. ## Execution Mode This skill defaults to **In-Process mode** for zero-latency direct disk access. No background server is required. ## Execution Protocol ### 1. Identify Search Profile Verify available profiles in `.agent/learning/vector_profiles.json`. The default profile is usually `wiki`. ### 2. Run Cleanup Note: The `--profile` flag is mandatory to ensure the correct collection and disk paths are loaded. ```bash python ./scripts/cleanup.py --profile wiki ``` ### 3. Verify Store Integrity (Optional) Run the consistency check to verify that remaining facts are still supported. ```bash python ./scripts/vector_consistency_check.py --profile wiki --topic .agent/learning/ ``` ## Rules - **Profile Sovereignty**: Always pass `--profile` to ensure the correct semantic space is pruned. - **API Integrity**: NEVER a