fixup! docs: sort the top-level directories into five sections by what the reader wants

README.md

@@ -114,7 +114,7 @@ box it gets:
 ## Quick start: an all-local swarm
 
 The whole swarm on one box — a hive plus every shared service. Good for a
-dev box or a single-host deployment; [`docs/swarm/`](docs/2-handbook/swarm/README.md)
+dev box or a single-host deployment; [`docs/2-handbook/swarm/`](docs/2-handbook/swarm/README.md)
 covers spreading a swarm across hosts.
 
 ```nix
@@ -173,7 +173,7 @@ once, top to bottom.
   → [reference](docs/2-handbook/reference/swarmctl-cli.md)
 - **per-hive** — each hive's dashboard (container state,
   rebuild queue) and `hivectl` for host-level administration and
-  container shells. → [`docs/web-ui/`](docs/2-handbook/web-ui/README.md) ·
+  container shells. → [`docs/2-handbook/web-ui/`](docs/2-handbook/web-ui/README.md) ·
   [hivectl](docs/2-handbook/tools/hivectl.md)
 
 You are an SSO user too: `swarmctl user add <you> --group admins`, and a
@@ -187,10 +187,10 @@ one becomes a homeserver admin within five minutes of that first login.
 pick the page for your task rather than reading front to back. Some
 common entry points:
 
-- connecting hives into a swarm → [`swarm/`](docs/2-handbook/swarm/README.md)
-- how config changes flow → [`agent-lifecycle/config-changes.md`](docs/2-handbook/agent-lifecycle/config-changes.md)
+- connecting hives into a swarm → [`2-handbook/swarm/`](docs/2-handbook/swarm/README.md)
+- how config changes flow → [`2-handbook/agent-lifecycle/config-changes.md`](docs/2-handbook/agent-lifecycle/config-changes.md)
 - trust boundary + threat model → [`trust-boundary/`](docs/2-handbook/trust-boundary/boundary.md)
-- what an agent's turn looks like → [`turn-loop/`](docs/4-implementation/turn-loop/README.md)
+- what an agent's turn looks like → [`4-implementation/turn-loop/`](docs/4-implementation/turn-loop/README.md)
 - every `services.hyperhive.*` option → [options reference](https://hyperhive.darkest.space/options/)
 
 ## Hacking on it