docs: complete scene 8 chat entry slice

web/README.md

@@ -180,8 +180,11 @@ claim boundaries and future work explicit, and end on the canonical defense
 discussion index rather than a benchmark or generic conclusion.
 
 Scenes 8 and 9 use the canonical prepared-authoring recording as their only
-execution evidence. Scene 8 is a full-screen conversation that establishes the
-external agent handoff; Scene 9 breaks the prepared authoring into five phases
+execution evidence. Scene 8 is a full-screen chat entry: 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. The handoff beat reveals the full prepared conversation;
+Scene 9 breaks the prepared authoring into five phases
 with the same conversation contracted into a synchronized bottom dock. Each
 phase opens its matching prepared tool group beneath a factual source, graph,
 repair, artifact, or deployment view. Neither scene calls workflow authoring
@@ -330,11 +333,11 @@ Scenes 8 and 9 are the prepared authoring story. They use deterministic data
 from the committed `projectPreparedAuthoring()` recording and never call
 workflow authoring RPC operations.
 
-- **Scene 8 (Agent Handoff)**: a full-screen prepared conversation that
-  establishes the external agent interface. The `request` beat shows the
-  operator requesting a report workflow; the `handoff` beat reveals the full
-  completed conversation with prepared `wf` tool groups across all authoring
-  phases.
+- **Scene 8 (Agent Handoff)**: a full-screen deterministic chat entry that
+  pre-fills the report-authoring request. Send is local presentation state and
+  reveals the first prepared Discover tool group; the `handoff` beat reveals
+  the full completed conversation with prepared `wf` tool groups across all
+  authoring phases. This is not a live LLM chat 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
@@ -342,8 +345,8 @@ workflow authoring RPC operations.
   current beat. There is no detached trace modal or second transcript.
 
 The authoring scenes consume deterministic prepared data and never call
-workflow authoring RPCs — only `workflow.health` infrastructure pings are
-permitted.
+workflow authoring RPCs. Scene 8 also skips live target probing so its request
+and Send path remain fully local; later execution scenes own live-run behavior.
 
 ### Demo Climax (Scenes 10–12)