drop hive and agent response fields the frontend never reads

docs/4-implementation/web-ui/agent-page.md

@@ -99,7 +99,7 @@ at a given viewport width. Two columns:
 
 Values throughout come from `GET /api/state`'s cold-load snapshot,
 kept in sync afterwards by the SSE stream (see Live view below) —
-`context_window_tokens` for the ctx badge tooltip, `qualified_label`
+`qualified_label`
 (the hive-qualified `name@domain` form, used for the browser tab title
 so two tabs from different hives are distinguishable; the header's own
 `◆ <label> ◆` stays short).
@@ -288,15 +288,14 @@ credentials arrive from the swarm secret store.
 
 - `GET /api/state` — cold-load snapshot (`StateSnapshot`) consumed by
   the frontend (`useAgentState.ts`) on page load. Includes `turn_state`,
-  `context_window_tokens`, `qualified_label`,
+  `qualified_label`,
   `model`, `model_source`, `effort`, `effort_source`, `links`, and
   other fields described inline throughout this document. All
   subsequent state updates arrive via SSE.
 - `GET /api/dashboard-state` — lean snapshot of agent-owned fields
   fetched once per running agent by the dashboard's container row to
   get fresh values without relying on hive-c0re's periodic file-reads.
-  Returns `{ status_text?, status_set_at?, ctx_tokens?, context_window_tokens,
-rate_limited, links }`. Only called when the container is running;
+  Returns `{ status_text?, status_set_at?, rate_limited, links }`. Only called when the container is running;
   skipped (muted badges) when stopped. Also accessible via the gateway
   at `/agent/<name>/api/dashboard-state`.
 - `GET /api/todos` — harness-local todos snapshot (loose-ends v2)

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

@@ -60,7 +60,7 @@ active; hash changes don't reload the page.
 container, sorted alphabetically by agent name; every container the
 rescan reports gets a row. Pulsing red banner at the top
 of this section if any two sub-agents hash to the same port
-(`port_conflicts` from `/api/state`): the operator must rename
+(derived client-side from the container ports): the operator must rename
 one of them and rebuild. `lifecycle::{spawn,rebuild}` also
 preflight this and refuse with a clear error message naming the
 conflicting agent.
@@ -117,7 +117,7 @@ pipeline) with an `onUpdate` callback 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 a refetch via the mount
 handle's `.refresh()` on every `rebuild_queue_changed` SSE tick (that
-event is a bare `{ seq }` trigger carrying no queue payload; both
+event is a bare trigger carrying no queue payload; 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
@@ -425,9 +425,8 @@ below — some endpoints aren't in it yet.
 - `POST /api/purge-tombstone/{name}` — wipe a tombstone's state dirs.
 - `POST /api/rebuild-queue/{id}/cancel` — drop a `Queued` entry.
   Refuses `Running` / terminal-state entries (in-flight
-  rebuilds can't be safely interrupted). Always 200; body is
-  `{"cancelled": true}` on a successful flip or
-  `{"cancelled": false}` when the entry wasn't in `Queued` state.
+  rebuilds can't be safely interrupted). Always 200 with an empty body, whether or not
+  the entry was in `Queued` state.
 - `POST /api/agent/{name}/mark-all-read` — ack all pending broker
   messages for `{name}`. Backfills `delivered_at` for rows
   not yet delivered and sets `acked_at = now`. Returns
@@ -436,8 +435,7 @@ below — some endpoints aren't in it yet.
 
 - `GET /api/dashboard/stream` — unified live event channel:
   broker `sent` / `delivered`, plus the mutation events listed
-  below. Each frame carries `seq`.
-  <!-- vale write-good.Passive = YES -->
+  below. <!-- vale write-good.Passive = YES -->
 
 ## Dashboard event channel
 
@@ -463,12 +461,12 @@ payload):
   `crash_watch` poll. Client upserts/removes by name and
   reads the pending overlay from `transientsState` since the
   payload doesn't carry it.
-- `rebuild_queue_changed` (seq) — **payload-free trigger**, fired on
+- `rebuild_queue_changed` — **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.
-- `tombstones_changed` (seq, tombstones: `Vec<TombstoneView>`) —
+- `tombstones_changed` (tombstones: `Vec<TombstoneView>`) —
   full snapshot of destroyed-but-state-kept agents. Emitted on
   destroy, purge, and revive. The K3PT ST4T3 tab subscribes.
 

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

@@ -39,15 +39,12 @@
   XSS-safe by construction the way the text-node `linkify` path is.
   Rendered `<a>`s are rewritten to `target="_blank"`.
 - `GET /api/state` → JSON snapshot the JS app renders into the
-  DOM. Includes a top-level `seq` (the dashboard event channel's
-  high-water mark at the moment the server assembled the snapshot);
-  clients use it to dedupe their buffered SSE traffic against
-  the snapshot (drop frames with `seq <= snapshot.seq`).
+  DOM.
 - `GET /api/dashboard/stream` (dashboard) / `GET /events/stream`
   (per-agent) → `text/event-stream` SSE for live updates. The
   dashboard stream carries broker `Sent` / `Delivered` (mirrored
   by a forwarder task from the broker's intra-process channel)
-  plus mutation events (`transient_set` / `transient_cleared`). Each frame carries a `seq`. The
+  plus mutation events (`transient_set` / `transient_cleared`). The
   agent's matching backfill endpoint is `GET /events/history` (last 2000
   `LiveEvent`s wrapped in `{ seq, events }`).
   **One unified channel**: browsers cap concurrent SSE