fix(confidence-engine): describe explored questions without implying resolution

components/reasoning-workspace.jsx

@@ -2002,7 +2002,7 @@ export default function ReasoningWorkspace({
                       {clarifiedQuestions.length > 0 && (
                         <div className="space-y-3">
                           <h2 className="text-[11px] font-semibold tracking-widest uppercase text-gray-500">
-                            Questions we have clarified
+                            Questions we've explored
                           </h2>
                           {clarifiedQuestions.map((node) => (
                             <div key={node.id} className="space-y-1">

docs/current-handoff.md

@@ -965,6 +965,37 @@ Returns JSON-serializable record with: five deconstruction arrays (`observations
 
 **Evidence file:** `.evidence-temp/headless-semantic/HS-03C-focused-E9.json`
 
-### Iteration 3 — Extract Focused Target Input (apparatus recovery)
+### Iteration 3 — UI Copy: Clarified → Explored (bounded heading change)
 
-The focused-investigation target-node extraction was purified into a standalone pure function `extractFocusedTargetInput(situationGraph, targetNodeId)` in the canonical helper. Deterministic test verified: known-node exact-match (1/1), unknown-node empty-string fallback (2/2), graph-immutable-side-effect (1/1), source-pattern integration verification (1/1) — total 5/5 PASS. Zero live model calls. Extraction was tested deterministically; the original Experiment 9 runtime graph and root cause remain unestablished.
+**Type:** Targeted UI copy change (Iteration 3 of bounded iteration loop). Zero live calls. Zero behaviour change.
+
+**Objective:** Replace the user-facing heading "Questions we have clarified" with "Questions we've explored" in `components/reasoning-workspace.jsx`. Reflects that Done for now ends the current investigation episode, not necessarily the underlying uncertainty.
+
+**What was changed:**
+- Line 2005 of `components/reasoning-workspace.jsx`: visible `<h2>` heading text replaced — `Questions we have clarified` → `Questions we've explored`
+- No code logic, no state transitions, no filtering or classification changes.
+
+**Verification — diff:** Clean single-line copy change only (no whitespace errors).
+
+**Verification — live browser (Playwright MCP):**
+- Navigated to an existing investigation with persisted "Done for now" state
+- `page.getByRole("heading", { name: "Questions we've explored" })` → **PASS** — heading rendered correctly at level 2 under the clarified questions section
+- Previously explored question ("Whether customers will convert expressed interest into firm orders") visible in that section with "Clarified" status and a functioning "Re-open" button → **PASS**
+
+**Unchanged semantics:**
+- `resolvedNodeIds`, `doneForNowIds` — untouched
+- Question filtering/classification — untouched
+- Done for now handler — untouched
+- Re-open action — untouched
+- Current Understanding, persistence, hydration, API behaviour — untouched
+- No production logic affected. Only user-facing heading text changed.
+
+**Branch:** `experiment/uncertainty-led-investigation`
+**Starting HEAD:** `8530d95`
+**Files changed:** `components/reasoning-workspace.jsx`, `docs/current-handoff.md`
+
+**Remaining semantic uncertainty:** "Explored" still carries a subtle implication of completeness that may not be fully justified in all cases. Whether users interpret "explored" as sufficiently provisional vs. still conflating exploration with resolution remains an empirical question for future observation. Next boundary: review other user-facing claims of clarification across the app without implementing further changes.
+
+**Targeted test:** NOT IDENTIFIED
+**Playwright heading:** PASS
+**Playwright Re-open:** PASS