docs: complete scene 9 assistant modal slice

docs/current_roadmap.md

@@ -171,8 +171,8 @@ Implementation order:
 24. Add a static slide/appendix shell only after presentation mode is clear.
     Astro remains an option, not the default next surface.
 25. Completed: presentation agent authoring story creates a canonical prepared
-    authoring recording, Scene 8 as an authentic full-screen conversation,
+    authoring recording, Scene 8 as an authentic single-beat full-screen
-    Scene 9 as a 5-phase lifecycle with synchronized chat dock, and route-level coverage
+    conversation, and Scene 9 as a 5-phase lifecycle with route-level coverage
     that never calls workflow authoring RPC operations during Scene 9
     navigation. Implementation:
     [`presentation agent authoring story`](historical/superpowers/plans/2026-07-11-presentation-agent-authoring-story.md).
@@ -202,14 +202,15 @@ Presentation visual audit, July 11:
 
 ## Completed: Presentation Recomposition And Authoring Story
 
-Scenes 8 and 9 are now implemented as authentic external-agent handoff and
+Scenes 8 and 9 are now implemented as authentic external-agent request and
-factual prepared-authoring proof. The canonical recording, full-screen Scene 8,
+factual prepared-authoring proof. Scene 8 is one local request-to-first-turn
-Scene 9 lifecycle with a synchronized chat dock, five factual phase visuals,
+beat; its obsolete `/handoff` route fails closed. Scene 9 keeps a persistent
-and route coverage are all in place. The obsolete receipt/trace modal was
+prepared assistant pane beside five factual phase visuals in an adaptive
-removed. Plans:
+approximately 35/65 split. The obsolete receipt/trace modal and lower chat dock
+were removed. Plans:
 [`presentation agent authoring story`](historical/superpowers/plans/2026-07-11-presentation-agent-authoring-story.md)
 and
-[`continuous authoring workspace`](historical/superpowers/plans/2026-07-11-continuous-authoring-workspace.md).
+[`Scene 9 assistant pane`](historical/superpowers/plans/2026-07-12-scene-9-assistant-modal.md).
 
 Recommended next visual slices:
 
@@ -272,9 +273,11 @@ separate activity after these surfaces are stable.
    reveals the first prepared authoring conversation without starting a
    workflow run. Implementation:
    [`Scene 8 chat entry`](historical/superpowers/plans/2026-07-12-scene-8-chat-entry.md).
-2. **Scene 9 assistant modal:** remove the lower chat dock, give the prepared
+2. **Completed: Scene 9 assistant pane:** replaced the lower chat dock with a
-   lifecycle canvas the available stage, and expose the synchronized authoring
+   persistent prepared-agent pane on the left and a dominant adaptive phase
-   conversation through an assistant-ui modal anchored on the left.
+   canvas on the right, starting near a 35/65 split. The Scene 8 handoff beat
+   was removed; the request route remains local and deterministic. Implementation:
+   [`Scene 9 assistant pane`](historical/superpowers/plans/2026-07-12-scene-9-assistant-modal.md).
 3. **Live/replay truth and run activation:** keep Scene 9 authoring evidence
    recording-backed, make Scenes 10–12 consume the active live timeline when a
    run exists, keep replay fallback for direct links or unavailable services,

docs/historical/superpowers/plans/2026-07-12-scene-9-assistant-modal.md

@@ -71,8 +71,8 @@
 
 ## Task 4: Browser Acceptance And Responsive Review
 
-- [ ] Use the running `pnpm dev` server if available; do not start a duplicate server or terminate the user's RPC server.
+- [x] Use the running `pnpm dev` server if available; do not start a duplicate server or terminate the user's RPC server.
-- [ ] Capture and inspect Scene 9 at 1280x720 and 1024x768 for at least these hashes:
+- [x] Capture and inspect Scene 9 at 1280x720 and 1024x768 for at least these hashes:
 
   ```text
   #scene/prepared-lifecycle/discover
@@ -80,25 +80,25 @@
   #scene/prepared-lifecycle/deployment
   ```
 
-- [ ] Verify the split state: assistant pane is on the left, phase visual is on the right, both are simultaneously visible with no overlap, the right pane is visibly dominant, no lower chat dock or detached receipt/trace modal remains, and no body scrollbar appears.
+- [x] Verify the split state: assistant pane is on the left, phase visual is on the right, both are simultaneously visible with no overlap, the right pane is visibly dominant, no lower chat dock or detached receipt/trace modal remains, and no body scrollbar appears.
-- [ ] Verify the assistant pane: title, current phase, prepared disclosure, conversation, and active tool group are readable; the pane scrolls internally if needed.
+- [x] Verify the assistant pane: title, current phase, prepared disclosure, conversation, and active tool group are readable; the pane scrolls internally if needed.
-- [ ] Verify beat changes update the active phase group and right-side visual together.
+- [x] Verify beat changes update the active phase group and right-side visual together.
-- [ ] Verify Scene 8 direct request route still works, Send reveals Discover locally, and `/handoff` no longer resolves as a valid Scene 8 route.
+- [x] Verify Scene 8 direct request route still works, Send reveals Discover locally, the footer shows `1 / 1`, and `/handoff` no longer resolves as a valid Scene 8 route.
-- [ ] Check browser console. The only accepted existing noise is the missing `/favicon.ico` request; there must be no React, modal, or layout errors.
+- [x] Check browser console. The only accepted existing noise is the missing `/favicon.ico` request; there must be no React, modal, or layout errors.
-- [ ] Store screenshots only under the ignored `web/apps/console/.visual-smoke/` directory.
+- [x] Store screenshots only under the ignored `web/apps/console/.visual-smoke/` directory.
 
 ## Task 5: Documentation, Review, And Archive
 
-- [ ] Update `web/README.md` to describe Scene 8 as a single deterministic chat-entry beat and Scene 9 as a 35/65 phase canvas with a persistent prepared-agent assistant pane.
+- [x] Update `web/README.md` to describe Scene 8 as a single deterministic chat-entry beat and Scene 9 as a 35/65 phase canvas with a persistent prepared-agent assistant pane.
-- [ ] Update `docs/current_roadmap.md`: mark the Scene 9 assistant-modal slice complete, note the Scene 8 handoff-route removal, and link this plan after archiving.
+- [x] Update `docs/current_roadmap.md`: mark the Scene 9 assistant-pane slice complete, note the Scene 8 handoff-route removal, and link this plan after archiving.
-- [ ] Search for stale wording and selectors:
+- [x] Search for stale wording and selectors:
 
   ```powershell
   rg -n "agent-handoff/handoff|Prepared operation|handoff beat|bottom dock|synchronized chat dock|prepared-lifecycle-scene__dock" web docs skills
   ```
 
-- [ ] Run the repository review skill on the complete diff. Fix correctness and scope findings; document judgement-call deferrals.
+- [x] Run the repository review skill on the complete diff. Fix correctness and scope findings; document judgement-call deferrals.
-- [ ] Run the final verification gate:
+- [x] Run the final verification gate:
 
   ```powershell
   pnpm --dir web test
@@ -108,14 +108,14 @@
   git status --short
   ```
 
-- [ ] Move this plan to `docs/historical/superpowers/plans/2026-07-12-scene-9-assistant-modal.md` and commit documentation/archive changes as `docs: complete scene 9 assistant modal slice`.
+- [x] Move this plan to `docs/historical/superpowers/plans/2026-07-12-scene-9-assistant-modal.md` and commit documentation/archive changes as `docs: complete scene 9 assistant modal slice`.
 
 ## Self-Review Checklist
 
-- [ ] Scene 8 has no obsolete `/handoff` beat or full-transcript duplicate.
+- [x] Scene 8 has no obsolete `/handoff` beat or full-transcript duplicate.
-- [ ] Scene 9 has one dominant right-side visual and one subordinate left assistant pane, both visible at once, not a lower dock or overlay modal.
+- [x] Scene 9 has one dominant right-side visual and one subordinate left assistant pane, both visible at once, not a lower dock or overlay modal.
 - [ ] The assistant pane uses generated assistant-ui/shadcn primitives where compatible and does not introduce a runtime or transport.
-- [ ] The modal content is factual prepared replay, not implied live execution.
+- [x] The assistant content is factual prepared replay, not implied live execution.
-- [ ] The current phase and active tool group stay synchronized across all five Scene 9 beats.
+- [x] The current phase and active tool group stay synchronized across all five Scene 9 beats.
-- [ ] The two panes remain synchronized when navigating between all five Scene 9 beats.
+- [x] The two panes remain synchronized when navigating between all five Scene 9 beats.
-- [ ] 1280x720 and 1024x768 screenshots were inspected, not merely captured.
+- [x] 1280x720 and 1024x768 screenshots were inspected, not merely captured.

docs/runbooks/defense-presentation.md

@@ -136,8 +136,9 @@ location.reload();
 
 When a stateful demo deep link is opened before this browser session has started
 a live run, the presentation selects the reviewed recording for that beat even
-if the loopback health probe succeeds. Start from the Scene 8 handoff action to
+if the loopback health probe succeeds. Scene 8's request and Send action remain
-run live; otherwise the typed interrupt, output, and trace links remain useful
+local replay behavior; start the live path from the Scene 10 run operation.
+Otherwise the typed interrupt, output, and trace links remain useful
 replay-backed entry points.
 
 ## Useful Deep Links

docs/superpowers/specs/2026-07-12-scene-8-chat-entry-design.md

@@ -199,7 +199,7 @@ Add or update tests for:
 
 - Real LLM or AI SDK execution;
 - workflow run start or resume;
-- Scene 9 assistant modal;
+- Scene 9 persistent prepared-agent assistant pane;
 - truth-badge scoping;
 - Scene 11 beat compression;
 - changes to the overall story order;

web/README.md

@@ -172,8 +172,8 @@ The console exposes `/present`, a 720p no-scroll defense compositor for the
 prepared `lda_report_workflow` story. It renders a 14-scene, multi-beat
 storyboard (expanded from the original 12-scene defense plan; items 13 and 14
 now cover evaluation and closing) with an adaptive aspect-ratio canvas, stable
-stage regions, discussion branches, one editorial canvas, a chat dock, and keyboard
+stage regions, discussion branches, one editorial canvas, persistent scene-aware
-navigation.
+assistant surfaces, and keyboard navigation.
 
 The final presentation beats frame the evaluation as bounded evidence, make
 claim boundaries and future work explicit, and end on the canonical defense
@@ -184,11 +184,11 @@ execution evidence. Scene 8 is a single full-screen chat-entry beat: its
 prefilled request is submitted locally, then reveals the first deterministic
 user, assistant, and Discover tool group. It is deterministic replay, not a live
 LLM chat, and does not start a workflow run. Scene 9 breaks the prepared
-authoring into five phases with the same conversation contracted into a
+authoring into five phases with a persistent prepared-agent assistant pane on
-synchronized bottom dock. Each
+the left and a dominant phase canvas on the right. The adaptive split starts
-phase opens its matching prepared tool group beneath a factual source, graph,
+near 35/65 and keeps the matching prepared tool group synchronized with each
-repair, artifact, or deployment view. Neither scene calls workflow authoring
+factual source, graph, repair, artifact, or deployment view. Neither scene calls
-RPC operations — they consume deterministic prepared data. Scenes 10 through
+workflow authoring RPC operations — they consume deterministic prepared data. Scenes 10 through
 12 use the canonical replay by default when no live target is available. When
 the resolved target is healthy, the same prepared run flow can execute through
 the public JSON-RPC operations and record live evidence using the same
@@ -338,9 +338,11 @@ workflow authoring RPC operations.
   or workflow run.
 - **Scene 9 (Prepared Workflow Lifecycle)**: a five-phase lifecycle
   (discover, draft, validate, artifact, deployment) with a compact phase rail
-  and one dominant factual product projection per beat. The Scene 8 thread
+  and one dominant factual product projection per beat. A persistent prepared
-  remains visible as a compact bottom dock; its active tool group follows the
+  assistant pane stays visible on the left while the phase canvas remains
-  current beat. There is no detached trace modal or second transcript.
+  dominant on the right; the starting split is approximately 35/65 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.
 
 The authoring scenes consume deterministic prepared data and never call
 workflow authoring RPCs. Scene 8 also skips live target probing so its request