docs: complete presentation live replay activation

docs/current_roadmap.md

@@ -283,11 +283,11 @@ separate activity after these surfaces are stable.
    [`Scene 9 staged message box`](historical/superpowers/plans/2026-07-12-scene-9-staged-message-box.md).
    The boundary is explicit: Scenes 10–12 own run activation, approval,
    resume, output, and trace evidence.
-3. **Live/replay truth and run activation:** keep Scene 9 authoring evidence
+3. **Completed: Live/replay truth and run activation:** Scene 10 exposes the
-   recording-backed, make Scenes 10–12 consume the active live timeline when a
+   prepared-run action outside the hidden chat, retries the existing health
-   run exists, keep replay fallback for direct links or unavailable services,
+   probe, starts live execution explicitly, and keeps direct links and failed
-   scope the truth badge to demo scenes, move the prepared-run action to Scene
+   services on truthful replay evidence. Implementation:
-   10, and correct the Scene 10 graph/proof projection.
+   [`presentation live/replay activation`](historical/superpowers/plans/2026-07-12-presentation-live-replay-activation.md).
 4. **Completed: Scene 11 compression:** reduce the typed-human-boundary scene to two
    beats: interrupt context and approval decision. Cancellation remains a
     decision outcome rather than a near-duplicate presentation beat.

docs/superpowers/specs/2026-07-12-presentation-live-replay-activation-design.md

@@ -1,6 +1,6 @@
 # Presentation Live/Replay Activation Design
 
-**Status:** Proposed
+**Status:** Implemented
 
 ## Goal
 

web/README.md

@@ -195,6 +195,23 @@ the public JSON-RPC operations and record live evidence using the same
 DemoRunFacts projection. Raw protocol payloads are available through the
 evidence receipt and inspector.
 
+Scene 10's operation beat exposes the explicit `Run prepared workflow` action
+even when a direct link is currently showing replay evidence. With a healthy
+target, it starts the live chain through the existing `/api/rpc` proxy. If the
+health probe fails, the surface shows the failure reason, offers `Retry live
+service`, and keeps `Play replay walkthrough` as an explicit fallback. The
+presentation does not silently replace a live failure with recorded evidence.
+
+For local live rehearsal, run both services:
+
+```powershell
+pnpm --dir web dev
+uv run wf-rpc-server --config examples/lda_report_workflow/wf.config.json --host 127.0.0.1 --port 8765
+```
+
+The browser runs on `5173`, the console server proxy runs on `8787`, and the
+workflow RPC server listens on `8765/rpc`.
+
 The presentation chat surface is source-owned and follows the AI Elements
 conversation/message/tool/prompt-action model. It currently renders the
 prepared timeline agent and approval flow; a future AI SDK driver should target