deploy the closure the swarm declares, read no forge head, drop the update badge

docs/web-ui/README.md

@@ -48,9 +48,9 @@ See [`config-changes.md`](../agent-lifecycle/config-changes.md#config-changes).
 
 **Start, stop, restart, or rebuild an agent.** Select one or more
 agents on 4G3NTS (select the icon) and use the selection bar, or use the
-per-agent `⋮` menu on a single row. Rebuilding re-applies that agent's
-current config; use it whenever an agent
-shows as "needs update."
+per-agent `⋮` menu on a single row. Rebuilding downloads and applies the closure the swarm
+declares for the agent again. The hive applies a changed declaration itself,
+so use it to retry one that failed.
 
 **Watch a build.** The dashboard's R3BU1LD QU3U3 tab shows the rebuild queue live, plus a
 streaming log of whatever's currently building. Useful right after

docs/web-ui/dashboard.md

@@ -65,9 +65,6 @@ one of them and rebuild. `lifecycle::{spawn,rebuild}` also
 preflight this and refuse with a clear error message naming the
 conflicting agent.
 
-`↻ UPD4TE 4LL` button appears above the containers list when any
-agent is stale.
-
 ## K3PT ST4T3 tab
 
 Passive / rare-interaction state. `kept.js` renders it from the
@@ -280,8 +277,7 @@ web server is down), so a single badge replaces the badge chain,
 the nav strip is empty, and status text / rate-limited / ctx
 badges disappear. The agent icon goes straight to the dimmed
 `/favicon.svg` fallback instead of attempting a doomed load from the
-container's URL. Static fields — `needs_update`, `deployed_sha`,
-`pending_reminders`, `parent`, `config` link — remain visible
+container's URL. Static fields — `pending_reminders`, `parent`, `config` link — remain visible
 regardless of run state.
 <!-- vale write-good.Passive = YES -->
 
@@ -296,7 +292,7 @@ below).
 restarts and gave up on its own) draws a red `✖ gave up` badge;
 otherwise a plain muted `■ not running` — a container an operator
 stopped deliberately. Both states read `running: false`; `failed` is
-the orthogonal fact (a fifth one alongside `paused`/`needs_update`/
+the orthogonal fact (a fourth one alongside `paused`/
 `needs_login`, same "independent flags, no state machine" shape —
 see `ContainerView`'s own doc comment) that tells them apart. An
 older hive-c0re without the field serves `failed: undefined`, which
@@ -304,14 +300,14 @@ reads falsy — degrades cleanly to the single `not running` badge.
 
 When the container is running, status badges follow — `⊘ rate
 limited` (red, while the harness parks itself after a 429), `needs
-login`, `needs update` — plus **one `◐ pending-state…` pill per
+login` — plus **one `◐ pending-state…` pill per
 active transient** (replaces buttons during operator-initiated
 start / stop / restart / rebuild / destroy). An agent can carry
 **multiple transients at once** — for example a lease-exempt `prebuild`
 running alongside a `stop_for_update` on the same agent — and each
 renders as its own independent badge instead of collapsing
 into one label, matching the existing multi-badge convention this
-line already uses for `paused`/`needs_update`/model/ctx.
+line already uses for `paused`/model/ctx.
 
 Any pending badge means the row is actually **running** something
 right now (see **Pending-badge derivation** below); every row
@@ -377,13 +373,6 @@ per-agent actions and navigation links. Contents:
 - `↻ R3BU1LD` — always available; queues a rebuild for this agent.
 - `DESTR0Y` / `PURG3` — destructive, each prompts for confirmation
   via the themed dialog (see **Themed dialogs** below).
-- `deployed:<sha> ↗` — present when the agent has a `deployed_sha`
-  and the forge is reachable; links the deployed commit on the forge
-  agent-configs mirror.
-
-`↻ UPD4TE 4LL` button appears above the containers list when any
-agent is stale. Banner pulses on each broker SSE event
-(`pulseBanner` with a 4s grace timer).
 
 **Build-queue summary banner** — when the job queue has any active
 work, a compact amber banner sits above the container list: `◐ build
@@ -491,7 +480,6 @@ below — some endpoints aren't in it yet.
 - `POST /api/{rebuild,kill,restart,start,destroy}/{name}` — lifecycle.
   `destroy` accepts `purge=on` to also wipe state dirs.
 - `POST /api/purge-tombstone/{name}` — wipe a tombstone's state dirs.
-- `POST /api/update-all` — rebuild every stale container.
 - `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