remove what no longer has a reader: build-log store, dashboard sent/delivered events, graph resource dep

docs/4-implementation/web-ui/dashboard.md

@@ -433,19 +433,14 @@ below — some endpoints aren't in it yet.
   `{ "marked": N }`. Agent name validated against
   `[a-z0-9_-]`, 1-63 chars; 400 on bad input.
 
-- `GET /api/dashboard/stream` — unified live event channel:
-  broker `sent` / `delivered`, plus the mutation events listed
-  below. <!-- vale write-good.Passive = YES -->
+- `GET /api/dashboard/stream` — unified live event channel: the
+  mutation events listed below. <!-- vale write-good.Passive = YES -->
 
 ## Dashboard event channel
 
 Wire vocabulary on `/api/dashboard/stream` (kind tag is in the JSON
 payload):
 
-- `sent` / `delivered` — broker traffic, mirrored from the
-  intra-process channel by a forwarder task. Both carry `id: i64`
-  (the broker row id) and `in_reply_to: Option<i64>` for thread
-  rendering.
 - `transient_set` (name, transient_kind, since_unix) /
   `transient_cleared` (name) — lifecycle action spinners. The
   client ticks the elapsed-seconds badge off `since_unix`

docs/4-implementation/web-ui/shape.md

@@ -52,9 +52,8 @@
   domain would exhaust this budget on a live hive; dispatching
   by `kind` on the client is a one-liner. Per-domain splits are
   reserved for high-volume sub-streams most consumers skip (none
-  exist yet). The broker's intra-process channel stays separate
-  from the dashboard channel to avoid coupling `recv_blocking_batch`
-  (hot path inside the harness turn loop) to presentation concerns.
+  exist yet). Broker messages don't ride it: the broker's intra-process
+  channel only wakes `recv_blocking_batch`.
   **SSE multiplexing**: the dashboard uses a
   `SharedWorker` (`stream-worker.js`) to hold one upstream
   `EventSource` per URL. All same-origin tabs share this worker