fix: scope workspace registry smoke cleanup

harness/docs/testing.md

@@ -59,20 +59,22 @@ the anti-bypass hooks. The glue depends on the Pi runtime (`pi.registerTool`,
 
 ## L2 — real LLM + real remote DB, manual / pre-release (NOT automated)
 
-**What:** end-to-end sessions with GLM 5.2 + the real Chirone DWH + pgvector, reached
-via REST over VPN. Plus the gate-glue validation (the part L1 cannot reach).
+**What:** end-to-end sessions with GLM 5.2 + the real Chirone DWH, plus the internal
+Qdrant/Ollama semantic services started by the ThothII stack. Plus the gate-glue
+validation (the part L1 cannot reach).
 
 **Dependencies (all required, skip cleanly if missing):**
 - LLM: Pi configured locally with GLM 5.2.
-- DB: the remote Supabase endpoints (DWH read-only + pgvector reader/writer), via VPN.
-- `harness/.env` populated with the API keys + CA path.
+- DB: the remote DWH endpoint, via VPN when required.
+- ThothII stack: internal Qdrant and Ollama services reachable from `core`.
+- `harness/.env` populated with the required DWH/model API keys + CA path.
 
 **Coverage (honest):** validates the assumption L1 cannot — that GLM 5.2 produces tool
 calls the gate accepts, that the skill's prompts lead to the expected interaction shape,
 that the gate glue handles real tool-call sequences (incl. Altro/Rifiuta/rollback),
 that value grounding and formula approval surface correctly on the real schema, that
-`memory save-one` upserts to the real pgvector. **Closes the skill→LLM→gate loop AND
-exercises the gate glue.**
+`memory save-one` upserts to the configured semantic store. **Closes the
+skill→LLM→gate loop AND exercises the gate glue.**
 
 **Honest limitation:** L2 is non-deterministic (the model may behave differently across
 runs) and slow/costly. It is a **pre-release safety net, not a regression gate**.