docs/web-ui.md: scrub #262 + #486 cookies (mara on #752)

docs/web-ui.md

@@ -408,7 +408,7 @@ body sits to the right with three stacked lines
   **icon-only nav strip** populated async from the agent backend
   (`📊 stats`, `🖥 screen` when GUI is enabled, `⬡ forge profile`,
   `↳ agent-configs mirror`, plus any agent-declared
-  `dashboardLinks` extras — issue #262). The dashboard JS fetches
+  `dashboardLinks` extras). The dashboard JS fetches
   `GET /api/agent/{name}/links`, a same-origin passthrough proxy
   that forwards the agent's own link list; the agent backend is
   the single source of truth. The frontend resolves each
@@ -458,7 +458,7 @@ body sits to the right with three stacked lines
     panel body.
   - Plain navigation links (config repo, forge profile,
     `dashboardLinks` extras) now live in the icon-only nav strip
-    on Line 1 — see above (issue #262). The agent's `config` link
+    on Line 1 — see above. The agent's `config` link
     goes to the repo root; the deployed sha shows separately on
     Line 1 as the `deployed:<sha>` chip, since the agent harness
     can't know its own deployed commit.
@@ -524,12 +524,12 @@ frosted-mauve bar slides up from the bottom of the viewport
   - `▶ ST4RT` — stopped agents only
   - `↻ R3BU1LD` — always available
   - `DESTR0Y` / `PURG3` — sub-agents only (disabled if manager selected)
-  - `⇡ M0V3 → ROOT` (#486) — promote selected agents to top-level
+  - `⇡ M0V3 → ROOT` — promote selected agents to top-level
     (parent = null); disabled when all selected are already at root.
     Backend `topology::set_parent` refuses moves it can't satisfy
     (e.g. moving the manager) and the refusal surfaces in the
     failure roll-up.
-  - `⇢ M0V3 → [select]` (#486) — inline picker available for any
+  - `⇢ M0V3 → [select]` — inline picker available for any
     selection size. The dropdown lists every container that isn't IN
     the selection itself nor a descendant of any selected agent
     (client-side BFS cycle prevention across the whole batch; the