diff --git a/docs/current-handoff.md b/docs/current-handoff.md
index e0af8f6..1d514fa 100644
--- a/docs/current-handoff.md
+++ b/docs/current-handoff.md
@@ -258,3 +258,91 @@ The immediate semantic pass has established a coherent working principle:
 > **The Engine should preserve what was said, how certain it was, who owns the proposition, and how strongly evidence supports relationships; then investigate missing evidence before inventing explanations or remedies.**
 
 Deterministic tests (22/22) verify the structural boundaries. Live-call evidence is bounded. No new experiment is run in this checkpoint.
+
+---
+
+## LIVE MANUAL WALKTHROUGH FINDING — Focused Progression UI (2026-08-26)
+
+### Verified during repaired Run A multi-turn focused-investigation flow
+
+The following was established by live manual walkthrough:
+
+```
+Run A presentation entry routing: FIXED
+Run A focused lifecycle continuity: FIXED
+focused question/form/response rendering inside Run A: FIXED
+same-node completed result reopen: FIXED
+multi-turn focused continuation: WORKING
+```
+
+### KNOWN UI PROGRESSION / OWNERSHIP DEFECT — Follow-up Selected-Question Duplication
+
+During the repaired Run A multi-turn focused-investigation flow:
+
+```text
+focused answer
+→ deconstruction
+→ "Questions this raises"
+→ user clicks the single proposed follow-up
+→ that follow-up becomes the active QUESTION above the textarea
+```
+
+The UI then continues to show the same previous proposal below under:
+
+```text
+QUESTIONS THIS RAISES
+[same question] → pick this question
+```
+
+So the selected follow-up is simultaneously displayed as:
+
+```text
+ACTIVE QUESTION
+```
+
+and:
+
+```text
+STILL-AVAILABLE ACTIONABLE FOLLOW-UP
+```
+
+This is visibly duplicated and demonstrates that the **proposal state** and **active-question state** are disconnected.
+
+**Product interpretation:** This is a KNOWN UI PROGRESSION / OWNERSHIP DEFECT, not merely a styling issue. The useful semantic progression is:
+
+```text
+answer → what this tells us → still unclear → proposed next question → user selects it → selected question becomes active
+```
+
+Once selected, its old representation must not continue to invite:
+
+```text
+→ pick this question
+```
+
+The old proposal should either become non-actionable provenance/history or cease being displayed as a candidate. Do not decide the final UI treatment in this checkpoint.
+
+### Related observation — Single follow-up / plural-candidate ownership
+
+Record also that `possibleFollowUpQuestions` currently contains **exactly one** proposed question, while the user-facing heading says **"Questions this raises"** and presents it as a selectable candidate. This raises a later product/ownership question:
+
+> Is this genuinely a menu of candidate questions, or is it the engine's proposed continuation of the current investigation?
+
+Do not resolve that question now.
+
+### Status of remaining items after this walkthrough
+
+```
+follow-up selected-question duplication:
+OPEN UI ISSUE
+
+focused → global ownership/integration:
+STILL OPEN
+
+Current Understanding incorporating focused learning:
+STILL OPEN
+```
+
+### Important separation note
+
+The latest second-turn semantic output exposed a separate reasoning issue around assumption attribution/frontier prioritisation. This must not be conflated with the UI duplication defect described above. They are orthogonal concerns — one is presentation state management, the other is semantic reasoning fidelity.