docs: close consolidated story review findings

docs/current_roadmap.md

@@ -205,11 +205,11 @@ Presentation visual audit, July 11:
 ## Completed: Presentation Recomposition And Authoring Story
 
 Scenes 7 and 8 now present an external-agent request through a scripted
-presentation surface and factual prepared-authoring proof. Scene 8 is one local request-to-first-turn
+presentation surface and factual prepared-authoring proof. Scene 7 is one local
-beat; its obsolete `/handoff` route fails closed. Scene 8 keeps a persistent
+request-to-first-turn beat; its obsolete `/handoff` route fails closed. Scene 8
-prepared assistant pane beside six factual phase visuals in an adaptive
+keeps a persistent prepared assistant pane beside six factual phase visuals in
-approximately 35/65 split. The obsolete receipt/trace modal and lower chat dock
+an adaptive approximately 26/74 split. The obsolete receipt/trace modal and
-were removed. Plans:
+lower chat dock were removed. Plans:
 [`presentation agent authoring story`](historical/superpowers/plans/2026-07-11-presentation-agent-authoring-story.md)
 and
 [`Scene 9 assistant pane`](historical/superpowers/plans/2026-07-12-scene-9-assistant-modal.md).

docs/runbooks/defense-presentation.md

@@ -166,7 +166,7 @@ visual hierarchy, chat mode, evidence mode, and fallback route.
 - Runtime providers:
   `http://127.0.0.1:5173/present#scene/architecture/runtime/focus/runtime-providers`
 - NodeUse:
-  `http://127.0.0.1:5173/present#scene/architecture/node-use/focus/node-use`
+  `http://127.0.0.1:5173/present#scene/architecture/overview/focus/node-use`
 - Agent handoff:
   `http://127.0.0.1:5173/present#scene/agent-handoff/request`
 - Prepared lifecycle:

docs/runbooks/presentation-visual-review.md

@@ -14,7 +14,7 @@ Open each URL in a browser at 100% zoom, 1280x720 viewport:
 Review these routes at `1024x768`, `1200x800`, and `1280x720`, always at 100%
 browser zoom:
 
-1. `/present#scene/architecture/node-use/focus/node-use`
+1. `/present#scene/architecture/overview/focus/node-use`
 2. `/present#scene/resume-output-evidence/trace`
 
 The logical canvas widths must be `960`, `1080`, and `1280` respectively.

web/README.md

@@ -364,7 +364,7 @@ workflow authoring RPC operations.
   (discover, draft, diagnose, repair, artifact, deployment) with a compact phase rail
   and one dominant factual product projection per beat. A persistent prepared
   assistant pane stays visible on the left while the phase canvas remains
-  dominant on the right; the starting split is approximately 35/65 and adapts
+  dominant on the right; the starting split is approximately 26/74 and adapts
   to the available width. Its active tool group follows the current beat. There
   is no lower chat dock, detached trace modal, or second transcript.
 

web/apps/console/src/presentation/authoring/authoring-recording.ts

@@ -44,7 +44,7 @@ export type PreparedAuthoringPhase = {
   readonly label: string;
   readonly commands: readonly PreparedAuthoringCommand[];
   readonly conversation: readonly AuthoringConversationTurn[];
-  /** Compact factual projection for Scene 9; command detail stays in the trace panel. */
+  /** Compact factual projection for the prepared lifecycle presentation. */
   readonly proof: readonly string[];
 };
 
@@ -52,7 +52,7 @@ const unknownPhase = (phase: never): never => {
   throw new Error(`unknown phase: ${phase}`);
 };
 
-/** Maps a scene 9 beat ID to the corresponding authoring phase. */
+/** Maps a canonical recording beat ID to its authoring phase. */
 export const authoringPhaseForBeat = (beatId: AuthoringPhaseId): AuthoringPhaseId => {
   switch (beatId) {
     case "discover":
@@ -275,8 +275,8 @@ export const authoringToolGroupId = (phase: AuthoringPhaseId): string =>
 /**
  * Projects the prepared recording into one stable assistant transcript.
  *
- * IDs depend only on phase and command position so the full Scene 8 thread and
+ * IDs depend only on phase and command position so the handoff thread and
- * compact Scene 9 dock retain DOM/message identity while later phases appear.
+ * prepared lifecycle assistant retain DOM/message identity as phases appear.
  */
 export const projectPreparedAuthoringThread = (
   throughPhase: AuthoringPhaseId = "deployment",