docs: title the knowledge repo and the forge index entry as swarm-level

The knowledge repo lives on the swarm's forge, shared by every hive; the
forge is the swarm's, not a hive's own.

docs/README.md

@@ -48,7 +48,7 @@ declarations.
 
 - **How do per-agent forge accounts work? What does `forge_notify` poll,
   and how does it format wake messages?** → [`integrations/forge.md`](integrations/forge.md)
-  (the hive's own Forgejo); [`tools/forge.md`](tools/forge.md) for the
+  (the swarm's Forgejo); [`tools/forge.md`](tools/forge.md) for the
   `hive-forge` CLI verbs agents actually call.
 - **How does the matrix-tuwunel container work? Multiple accounts per
   agent?** → [`integrations/matrix.md`](integrations/matrix.md) (the homeserver);
@@ -58,7 +58,7 @@ declarations.
   the PAT injected?** → [`integrations/github.md`](integrations/github.md)
   (operator content up top; the `gh`/git-push + notification-poller
   mechanics are in a collapsed "Implementation" section at the bottom).
-- **What's `/knowledge`? How does the hive-wide knowledge repo sync,
+- **What's `/knowledge`? How does the swarm-wide knowledge repo sync,
   and how do I contribute a document?** → [`integrations/knowledge.md`](integrations/knowledge.md).
 - **What does `hivectl` do? Provisioning, gateway users, container
   shells?** → [`tools/hivectl.md`](tools/hivectl.md) (the curated guide);

docs/integrations/knowledge.md

@@ -1,4 +1,4 @@
-# Hive-wide knowledge repository
+# Swarm-wide knowledge repository
 
 `internal/knowledge` on the forge is a shared reference doc repo
 readable by every agent. hive-c0re clones it to the host and