fix: scope workspace registry smoke cleanup

harness/README.md

@@ -22,16 +22,19 @@ The `tht` command is now on PATH. Node ≥ 20 is needed for the gate JS tests
 
 ```bash
 cp .env.example .env
-# fill in: THT_PROFILE, THT_DB_*, THT_DWH_API_KEY, THT_VEC_API_KEY,
-#          THT_VEC_WRITE_API_KEY, THT_SSL_CA, THT_OLLAMA_URL, ...
+# fill in: THT_PROFILE, THT_DB_*, THT_DWH_API_KEY, THT_SSL_CA, ...
 ```
 
 Keys are never logged; URLs are fine. Rotate any key that appeared in chat.
 
 ### `workspaces/<name>.yaml`
 
-A workspace wires the relational DWH + the pgvector (dual-key) + embeddings + evidence.
-See `workspaces/tht.example.yaml`. `${THT_*}}` tokens expand from `.env`.
+A schema-v3 workspace wires the external relational DWH to one internal Qdrant collection
+and the internal Ollama embedding model. Evidence paths remain workspace-local, while Qdrant
+stores the derived semantic projection for schema, Evidence, Memory, and solved-question
+records. The legacy files under `workspaces/` are retained as migration fixtures; new
+operator-facing descriptors live in the workspace Git registry. `${THT_*}` tokens expand
+from `.env`.
 
 > **DB support (MVP):** the `direct` transport supports **PostgreSQL only** (psycopg2
 > driver, `pg_*` catalog introspection, postgres-dialect sqlcheck/EXPLAIN). The central
@@ -130,7 +133,7 @@ tht/                 Python package (CLI + workflow + phase + decisions + db/res
 .pi/                 Pi project (settings, prompts, themes, extensions/tht-gate.js + gate/)
 workflow.yaml        single source of workflow truth (F2)
 workspaces/          workspace YAML definitions (D3)
-scripts/             reader/writer RPC SQL for pgvector (D11)
+scripts/             retained legacy SQL fixtures and workspace utilities
 tests/               L0 (testcontainers), L1 (logic + builders), L2 (real model + DB)
 docs/                testing guide + workflow editing
 ```