docs: record presentation visual follow-up pass

docs/current_roadmap.md

@@ -264,8 +264,10 @@ Recommended next visual slices:
    and a light prepared lifecycle canvas with synchronized secondary chat.
    Implementation:
    [`Scenes 7-9 editorial focal proof`](historical/superpowers/plans/2026-07-12-scenes-7-9-editorial-focal-proof.md).
-10. Next: revise the remaining visual outliers only when a screenshot identifies
-    a concrete hierarchy, overflow, or factual-readability problem.
+10. Completed: revise the remaining visual outliers only when a screenshot
+    identifies a concrete hierarchy, overflow, or factual-readability problem.
+    Implementation:
+    [`presentation follow-up visual/story pass`](historical/superpowers/plans/2026-07-13-presentation-followup-visual-story-pass.md).
 
 ## Next: Scene 8–14 Defense Recomposition
 
@@ -328,12 +330,15 @@ separate activity after these surfaces are stable.
    live run facts. Distinguish declared, selected, read, and produced files;
    do not imply file reads without evidence.
 
-10. **Active plan: presentation follow-up visual/story pass:** clarify Scene 1
-    and the lifecycle-to-authoring narrative, give Scenes 7 and 9 a stronger
-    dominant artifact, make the Scene 10 graph easier to present, and densify
-    Evaluation and Conclusion beats without inventing evidence.
+10. **Completed: presentation follow-up visual/story pass:** clarified Scene 1
+    and the lifecycle-to-authoring narrative, gave Scenes 7 and 9 a stronger
+    dominant artifact, made the Scene 10 graph easier to present, and densified
+    Evaluation and Conclusion beats without inventing evidence. The dated
+    review records the remaining factual input-browser, live-E2E, and full
+    screenshot-inspection follow-ups:
+    [`presentation follow-up visual review`](runbooks/presentation-followup-visual-review.md).
     Implementation plan:
-    [`presentation follow-up visual/story pass`](superpowers/plans/2026-07-13-presentation-followup-visual-story-pass.md).
+    [`presentation follow-up visual/story pass`](historical/superpowers/plans/2026-07-13-presentation-followup-visual-story-pass.md).
 
 Presentation wishlist / defense readiness:
 

docs/runbooks/presentation-followup-visual-review.md

@@ -0,0 +1,78 @@
+# Presentation Follow-Up Visual Review
+
+Review date: 2026-07-13
+
+This record closes the visual/story follow-up pass described by
+[`presentation follow-up visual/story pass`](../historical/superpowers/plans/2026-07-13-presentation-followup-visual-story-pass.md).
+It records what was checked, what is now presentable, and what remains a
+factual or product follow-up rather than silently treating it as solved.
+
+## Verification
+
+- Presentation route contract: 7 changed routes assert one exact heading, one
+  primary visual region, and no outer document scroll.
+- Focused evaluation, conclusion, and opening tests: 16 passed.
+- Workflow graph tests: 34 passed.
+- Full web gate: console 754 passed; RPC 52 passed and 6 skipped; server 46
+  passed.
+- Full web typecheck and build passed; the build retains the known Vite chunk
+  size warning.
+- Rehearsal capture: 42 routes at both `1280x720` and `1024x768` (84 PNGs).
+- Typecheck: `pnpm --dir web typecheck` passed.
+- Browser smoke: checked at `1280x720` and `1024x768` for the workflow graph,
+  evaluation findings, conclusion, and Scene 1 opening.
+- Workflow graph: React Flow initializes with a measured `fitView`; all ten
+  nodes and both outcome branches remain inside the graph frame at both target
+  viewports.
+
+## Fixed Visuals
+
+| Area | Result |
+|---|---|
+| Scene 1 opening | Product goal, implementation boundary, and planner/tool-surface/runner decomposition are distinct. The opening caption remains editorial and borderless; its row sizes to content instead of clipping the lower padding. |
+| Scene 5 to 7 story | Lifecycle vocabulary now leads into authoring and repair rather than presenting authoring as an isolated diagnostic screen. |
+| Scenes 7 and 9 | Authoring and prepared-lifecycle evidence use a dominant artifact with secondary assistant/support surfaces. |
+| Scene 10 graph | The graph is horizontal, factual, selectable, draggable/zoomable, and fit to the initialized React Flow viewport. Outcome shapes and edge labels remain visible. |
+| Scene 13 findings | Six findings use a readable 3x2 layout with icons, campaign size, outcome counts, and the bounded-evidence statement visible together. |
+| Scene 14 conclusion | The typed substrate and closing boundary are dominant; non-claims and future-work layers recede without being removed from their own beats. |
+
+## Remaining Findings
+
+### FACTUAL
+
+- Scene 10 input remains a prepared-run manifest, not a factual file browser
+  distinguishing declared, selected, read, and produced files. This remains a
+  separate roadmap item.
+- The prepared revision-request replay uses
+  `run_recorded_lda_report_revision`, while the submitted replay uses
+  `run_recorded_lda_report`. Do not describe the revision recording as the same
+  persisted run until a same-run recording is available.
+
+### PRODUCT
+
+- Live Scene 10-12 execution is health-checked and connectable, but still needs
+  a complete rehearsed start -> interrupt -> resume -> output -> trace path on
+  the running workflow server.
+- The presentation chat remains a scripted/replay product surface. A live LLM
+  driver and streaming agent conversation are future work.
+
+### BLOCKED / DEFERRED
+
+- A full manual inspection of every screenshot generated by the 42-route,
+  two-viewport rehearsal script remains a rehearsal activity, not a claim that
+  every beat has been visually hand-approved.
+- The final defense story-flow review and presenter companion assets remain
+  separate from this visual pass.
+
+## Rehearsal Commands
+
+```powershell
+pnpm --dir web test -- --run
+pnpm --dir web typecheck
+pnpm --dir web build
+./scripts/presentation-rehearsal.ps1
+```
+
+Use [`defense-presentation.md`](defense-presentation.md) for live/replay
+fallbacks and [`presentation-rehearsal-matrix.md`](presentation-rehearsal-matrix.md)
+for the route-by-route speaking line and evidence pointer.