docs: stop asserting DagView/NodeView after their deletion

The deletion PR removed the types but left ~10 sites still describing
them. Two are real breakage rather than staleness: rustdoc intra-doc
links to deleted items ([NodeView::kind] and [Self::snapshot] in
job_queue/mod.rs). Neither clippy --all-targets -D warnings nor cargo
test resolves intra-doc links, so the tree was green with both already
dangling.

The rest reassert facts the deletion made false: docs/coordinator.md
documented the event as RebuildQueueChanged { seq, queue: [DagView...] }
with a per-node field list, and three sites pointed at the removed
/api/state.rebuild_queue endpoint.

One is pointer rot rather than a rename, and no grep for a deleted name
finds it: SchedulesChanged justified itself as "same snapshot-shape
rationale as RebuildQueueChanged" -- which the deletion turned into the
one event that is not a snapshot. Repointed at TombstonesChanged /
MetaInputsChanged, in both the Rust doc and the dashboard doc.

Two are pre-existing and strictly out of scope, swept under the
pfadfinderregel because the same grep surfaced them: hive-sh4re/README
advertised a jobs module that crate has not had since the host-sock
split, and hive-host-sock/README claimed its own payload types live in
hive-sh4re.

Docs and comments only -- no behaviour, no API, no test changes.

docs/web-ui/dashboard.md

@@ -225,12 +225,10 @@ does not render the queue itself; it just mounts the element and
 listens for its `hive-jobq-graph-update` event to drive the two things
 below it that the generic view doesn't show. The component owns
 fetching, cold and live: `GET /api/jobq/graph` on mount, and
-`.refresh()` on every `rebuild_queue_changed` SSE tick (that event
-still carries its own `Vec<QueueEntry>` payload — `DagView`-shaped,
-also read by `hivectl`'s own wait/progress loop, a separate migration
-— on the wire, but neither dashboard page reads it anymore; both
-treat the tick as a pure refetch trigger against the generic
-endpoint).
+`.refresh()` on every `rebuild_queue_changed` SSE tick (that event is a
+bare `{ seq }` trigger — it carried a typed queue snapshot until every
+consumer had moved to the generic endpoint, and now carries none; both
+dashboard pages treat the tick as a pure refetch trigger).
 
 Each row is one root graph node (`parent: null`); a multi-step op's
 per-agent subgraphs and sub-steps render as nodes within that one
@@ -900,7 +898,8 @@ fetch entirely.
   life). Two consequences for anything rendering it:
 
   - The label vocabulary is **open** — it is the node's own wire tag
-    (`NodeKind::as_str`, the same strings `NodeView.kind` carries),
+    (`NodeKind::as_str`, the same strings the graph wire's node
+    labels carry),
     not a fixed set. Treat it as an opaque display string; do not
     switch on specific values. `restarting` in particular no longer
     exists, because no node kind is unique to a restart.
@@ -1441,19 +1440,19 @@ payload):
   `crash_watch` poll. Client upserts/removes by name; the
   pending overlay is read from `transientsState` since the
   payload doesn't carry it.
-- `rebuild_queue_changed` (seq, queue: `Vec<QueueEntry>`) —
-  full snapshot of the rebuild queue on every mutation (enqueue,
-  state transition, dedup collapse, terminal-history trim).
-  Same snapshot-over-diff rationale as `tombstones_changed` /
-  `meta_inputs_changed`: the list is small and the client renders
-  each DAG's multi-agent shape from its own `nodes` (no cross-DAG
-  grouping). Cold-loaded from `/api/state.rebuild_queue`.
+- `rebuild_queue_changed` (seq) — **payload-free trigger**, fired on
+  every queue mutation (enqueue, state transition, dedup collapse,
+  terminal-history trim). Unlike the snapshot events below it ships
+  no state at all: the client re-fetches `GET /api/jobq/graph`, which
+  is where it reads the queue from cold too. There is no
+  `/api/state.rebuild_queue` — it went with the typed projection.
 - `schedules_changed` (seq, schedules: `Vec<WireSchedule>`) —
   full snapshot of all scheduled prompts. Emitted after every
   operator mutation via the `/api/schedules` surface (new /
   edit / cancel / fire-now) and after the worker fires or
   rearms a row. Same snapshot-shape rationale as
-  `rebuild_queue_changed`. The SCH3DUL3S tab subscribes and
+  `tombstones_changed` / `meta_inputs_changed` (small list, no
+  add/remove races). The SCH3DUL3S tab subscribes and
   re-renders `schedulesState` on receipt; tab activation still
   re-fetches as a safety net for approval-path inserts and
   disconnect windows.