docs: the swarm and services pages become overviews

The controller's status, queue, AGENTS.md and forge-webhook details move to
4-implementation/swarm/controller.md. The metrics, logs and OTEL detail moves to
4-implementation/swarm/telemetry.md. Each leaves a short operator blurb with the
options to touch, and links into the moved text are updated.

swarm-controller/README.md

@@ -44,7 +44,7 @@ The swarm's control plane. The swarm UI and `swarmctl` are its clients.
 - **Config PR status** — each agent's open config-repo PR, cached from forge
   webhooks (`GET /api/config-prs`, `/api/agents/{name}/config-pr`).
 - **Swarm-wide forge objects and webhooks** →
-  [`docs/2-handbook/swarm/README.md`](../docs/2-handbook/swarm/README.md#swarm-wide-forge-objects).
+  [`docs/4-implementation/swarm/controller.md`](../docs/4-implementation/swarm/controller.md#swarm-wide-forge-objects).
 - **Scheduled prompts** — named prompts for one or more agents, kept in
   the `schedule-definitions` KV bucket and written into each agent's key of
   `agent-schedules`, both of which this daemon alone writes
@@ -80,7 +80,7 @@ The swarm's control plane. The swarm UI and `swarmctl` are its clients.
   (`PUT /api/agents/{name}/agents-md`). `POST /api/agents` can set the text the
   file starts with (`agents_md`), stored in the `agents-md-initial` bucket for
   the harness to write when no file exists →
-  [`docs/2-handbook/swarm/README.md`](../docs/2-handbook/swarm/README.md#an-agents-agentsmd).
+  [`docs/4-implementation/swarm/controller.md`](../docs/4-implementation/swarm/controller.md#an-agents-agentsmd).
 - **Review classifier** — try-outs from the swarm UI and reviews on review
   requests, the requested reviews not yet finished, in the `review-requests`
   work-queue stream, and the newest 100 finished runs, one document in the