remove the forge links from the hive dashboard and the agent page

Each agent row on the hive dashboard, and the agent page's link menu, linked
to the agent's forge profile and its config repo. Both are gone, with what
only they used:

- hive-agent no longer builds the two links, the `Forge` link kind, or the
  `forge_public_url` field of its state, and no longer reads
  `HIVE_FORGE_PUBLIC_URL`. The agent page's link menu and the dashboard row's
  icon strip (which skips a forge link an agent not yet rebuilt still sends)
  drop their forge handling.
- hive-c0re's dashboard state no longer carries `forge_public_url`.
- `HIVE_FORGE_PUBLIC_URL` is no longer forwarded to agents through the meta
  flake (the forwarded-variable list, its test fixture, the controller's
  settings and the VM test), so the next meta flake render differs by that
  one line. hive-c0re still reads it for the forge URL a hive publishes, so
  `swarm.forge.publicUrl` stays, with its description corrected.
- The docs stop describing the links.

docs/2-handbook/agents/web-page.md

@@ -81,14 +81,11 @@ at a given viewport width. Two columns:
   - **Links badge** (`🔗`): opens a popover listing `↑ dashboard`
     (back-link to the host dashboard, `${dashboardBase}`)
     followed by this agent's `agent_links()`-sourced navigation (stats,
-    screen when VNC is enabled, forge profile + config-repo mirror when
-    the agent has a forge account, any `services.hyperhive.agent.dashboardLinks`
+    screen when VNC is enabled, any `services.hyperhive.agent.dashboardLinks`
     extras) — all as real `<a>` elements, not a `Dropdown`-style
     command list, so ctrl/middle-click and "copy link address" keep
     working. Each `AgentLink.kind` resolves differently: `container` →
-    same-origin path; `forge` → `state.forge_public_url + url`, and
-    hive-agent drops the link entirely when that's unset (never guessed from
-    `<host>:3000`); `external` → already absolute. Same source
+    same-origin path; `external` → already absolute. Same source
     (`GET /api/state`'s `links` field) also feeds
     `DashboardState.links` for the dashboard card's icon strip —
     `agent_links()` in hive-agent is the single source of truth for

docs/2-handbook/hives/README.md

@@ -45,8 +45,8 @@ covers it.
 
 **Check on an agent.** 4G3NTS shows every container as a row: name, whether
 it's running, what it's doing (a live status pill such as `rebuilding…` or
-`starting…` while something's in flight), and quick links (stats, screen,
-forge profile). Select the name to open its terminal and watch it work.
+`starting…` while something's in flight), and quick links (stats, screen).
+Select the name to open its terminal and watch it work.
 
 **Review a config change.** Agent config changes (new packages, env vars, MCP
 servers) are pull requests on the agent's `agent-configs` repo. Review and

docs/2-handbook/hives/dashboard.md

@@ -197,9 +197,8 @@ fetch entirely.
 **icon-only nav strip** plus live agent-owned state, all populated
 async from a single `GET /api/dashboard-state` call to the agent's
 own hive-agent. The response (`DashboardState`) carries: `links` (nav
-strip entries — `📊 stats`, `🖥 screen` when GUI is enabled, `⬡ forge
-profile`, `↳ agent-configs mirror`, plus any agent-declared
-`dashboardLinks` extras), `status_text` / `status_set_at` (agent
+strip entries — `📊 stats`, `🖥 screen` when GUI is enabled, plus any
+agent-declared `dashboardLinks` extras), `status_text` / `status_set_at` (agent
 self-reported status — the `(set N ago)` chip carries a `data-set-at`
 stamp and ticks every 30s to stay fresh across the long-lived keyed row
 cache), `rate_limited`, `ctx_tokens` / `context_window_tokens`
@@ -216,11 +215,9 @@ per-agent harness — TCP or unix-domain depending on the agent's
 `docs/4-implementation/networking/gateway.md::Per-agent unix-socket upstream`).
 Gateway-off is the flag-absent fallback (a dashboard served outside a
 hyperhive deploy): base URL is
-`http://<host>:<container.port>` (direct TCP). Forge
-links resolve against `state.forge_public_url` (sourced from
-`services.hyperhive.swarm.forge.publicUrl`) and disappear entirely when
-that's unset — never guessed from `<host>:3000`. External links are
-already absolute. The same base URL drives the primary agent-name
+`http://<host>:<container.port>` (direct TCP). External links are
+already absolute. The row has no forge links: an agent's forge profile
+and config repo are on the forge itself. The same base URL drives the primary agent-name
 link + favicon fetch, so the whole row routes through the gateway
 as a unit.
 <!-- vale write-good.Passive = YES -->

docs/4-implementation/networking/gateway.md

@@ -431,9 +431,7 @@ when `StateSnapshot.gateway_enabled` is true, and direct
 every hive, so the direct shape is a fallback for the variable being unset.
 Three render sites follow it: the agent-name link, the favicon fetch
 (`<url>/icon`), and the nav-strip `container`-kind links from
-`DashboardState.links` (`GET /api/dashboard-state`). Forge links come from
-`swarm.forge.publicUrl`; with it unset the dashboard hides them rather than
-guess. See `docs/2-handbook/hives/dashboard.md::Container row` for the frontend side.
+`DashboardState.links` (`GET /api/dashboard-state`). See `docs/2-handbook/hives/dashboard.md::Container row` for the frontend side.
 
 ### Dialing another vhost by name (`verifiedProxyTo`)