docs: record presentation recomposition initiative

docs/current_roadmap.md

@@ -190,6 +190,45 @@ Presentation visual audit, July 10:
 - Completed: Scenes 13 and 14 now close with a bounded evaluation board,
   contribution boundary/future-work map, and canonical defense-question index.
 
+## Planned: Presentation Recomposition And Authoring Story
+
+The presentation needs a deck-wide compositional pass, not more isolated
+opacity tweaks. A scene should establish an overview, then give one object the
+stage while supporting evidence moves aside, exits, or enters as needed. A
+focused object may expand into an inspectable graph, command/result surface, or
+discussion point before the next object takes focus. Comparisons remain visible
+when comparison is the point; unrelated support does not remain on stage by
+default.
+
+- Establish a reusable overview -> focus -> transition grammar across the
+  presentation. Motion should communicate spatial ownership, not merely dim
+  inactive elements. Reserve cyan workflow evidence for the demo range; use
+  editorial ink, paper, and amber outside it.
+- Recompose Scenes 1 through 7 around that grammar. Scene 2 should sequence
+  one-off chat/tool actions before durable automation. Scene 3 should stage
+  the left and right positioning panes before the substrate resolves between
+  them. Scene 6 should let architecture blocks expand into child figures.
+  Scene 7 should begin with the five-stage authoring overview, then focus each
+  stage with concrete command, result, diagnostic, or graph evidence.
+- Make Scene 8 a full-screen assistant-ui `Thread` that establishes the
+  external planner interface with no workflow chrome competing for attention.
+- Make Scene 9 the deterministic authoring proof. It uses a collapsible
+  assistant-ui `AssistantModal` opened by an `Agent trace` trigger over the
+  workflow canvas. Each authoring phase contains multiple literal `wf` tool
+  calls, then updates the main lifecycle/graph projection:
+  1. discover sources, capabilities, and schemas;
+  2. create the draft, steps, and outcome routes;
+  3. bind, validate, diagnose, and repair;
+  4. compile and inspect the immutable artifact;
+  5. create and validate the deployment.
+  Scene 10 begins only after that prepared deployment is legible.
+- Treat broken trace-frame display as a blocking product defect before the
+  run/evidence arc is redesigned around trace proof. Diagnose it separately
+  with a regression test and use factual run/trace data from the console path.
+- Recut crowded multi-beat scenes, including Scenes 13 and 14, so their beats
+  use distinct dominant artifacts instead of permanently rendering a complete
+  board or map with only minor emphasis shifts.
+
 Recommended next visual slices:
 
 1. Completed: Opening visuals rebuilt Scenes 1 and 2 around concrete diagrams