the meta flake takes docs from the pinned hyperhive input

docs/swarm/builder.md

@@ -30,10 +30,6 @@ Where it runs and how it's enabled: [`services.md`](services.md#builder).
    - `hyperhive` and `nixpkgs`: the sources the builder's own host was
      deployed with (`c0re.hyperhiveFlake`, `c0re.nixpkgsFlake`). A hive's meta
      flake pins `hyperhive` by forge URL and rev instead.
-   - `hyperhive-docs`: the `docs/` source a hive on that host renders into its
-     meta flake (`c0re.hyperhiveDocs`). The check sets
-     `services.hyperhive.agent.docs.source` from it, as the meta flake does,
-     since the `hyperhive` source has no `docs/`.
    - `agent`: `git+https://<forge>/agent-configs/<agent>?ref=refs/pull/<pr>/head&rev=<head>`.
      A build has one hour.
 4. The reply is the system closure's store path, or the last lines `nix`

docs/turn-loop/config.md

@@ -20,9 +20,8 @@ markdown is readable during every turn.
 Off by default for every agent, ruth included. An agent opts in by adding the
 line above to its `agent.nix`.
 
-The `docs/` source is a narrow flake input (`hyperhive-docs`) tracked
-separately from the main `hyperhive` flake so editing docs re-locks only
-that input — not every agent's container gets rebuilt on a doc-only change.
+The docs come from the pinned `hyperhive` input (the `reference-docs` package
+built from its `docs/` tree), so they match the hyperhive rev the host runs.
 
 ## Agent icon