hive ui: remove the counters on the tabs

The pills on 4G3NTS, R3BU1LD QU3U3 and K3PT ST4T3, the poll that fed them, the
two count helpers, their styles, and the tab strip's unused badge option.

docs/web-ui/dashboard.md

@@ -106,8 +106,7 @@ build log history — is two tabs of the dashboard: **R3BU1LD QU3U3**
 dashboard's one tab strip, `/api/state` snapshot and
 `/api/dashboard/stream` subscription serve them, with
 `rebuild_queue_changed` on the stream alongside the dashboard's other
-kinds. The count pill on
-R3BU1LD QU3U3 is the number of rebuilds in flight.
+kinds.
 The 4G3NTS tab does **not** read the graph endpoint, by design — the swarm
 view stays independent of job-queue internals. Its per-agent pending
 badges are transient-only, and its queue-summary banner reads the much
@@ -157,7 +156,7 @@ the tree — one per lifecycle state, matching the row glyphs — lets the
 operator narrow which root groups render; unchecking a state re-fetches
 `GET /api/jobq/graph?states=<checked, comma-joined>` rather than
 hiding rows client-side, so the `onUpdate` callback's node list (and
-everything downstream of it — the count pill, the live-log panel) only
+everything downstream of it — the live-log panel) only
 ever sees what's actually shown. Filtering is by a **root's own**
 state, which is already its subtree's rolled-up answer, so the filter
 keeps or drops a whole group, never splitting mid-tree. Default selection is
@@ -175,7 +174,7 @@ Below the queue, a **live build-log panel** (`#rebuild-live-log`,
 inline — collapsible, with a live/ok/fail badge and a `↓ raw`
 download. It's keyed to the first `Running` node (in wire order)
 whose `payload.data.build_log_id` has a value — read from the `onUpdate`
-callback's node list, same source as the count pill, no separate
+callback's node list, no separate
 fetch — and **polls** `GET /api/build-log/{id}` every 2s
 (`fetchAndRenderLiveLog` / `liveLogPollTimer`); not an `EventSource`
 (that's the BUILD L0GS tab's own per-row expand view below — `GET