docs: make review classifier page generic over swarms

Drop the swarm-specific reviewer agent name and the hyperhive-repo
approval count from the architecture page and its index line.

docs/swarm/review-classifier.md

@@ -11,9 +11,10 @@ rules that the repo itself defines, and posts the result as a forge review.
 A small model answers one rule at a time, so mundane rule checks come out
 the same way on every PR.
 
-It doesn't replace argus's review. argus reviews a PR only once the
-classifier has passed it, and argus runs on a bigger model. The classifier
-takes the cheap, repetitive checks off argus.
+It doesn't replace a full review by a human or agent reviewer. A swarm can
+request that review only once the classifier has passed the PR, and use a
+larger model there. The classifier takes the cheap, repetitive checks off
+that reviewer.
 
 ## Repo configuration
 
@@ -189,7 +190,8 @@ changes, and the table is the review's body. An illustrative table:
 
 The approval is a real one: it counts toward a repo's required approvals
 like any other ([`pr-review-gate.md`](../process/pr-review-gate.md)). The
-hyperhive repo requires more approvals to account for it.
+Repos that rely on it typically raise their required approval count to
+account for it.
 
 ## Runtimes
 
@@ -284,8 +286,8 @@ These get settled, and filled in here, as the work reaches them:
   separate from the agents' on the existing dashboards.
 - **Async message medium.** Which queue subjects or streams carry the
   messages between `swarm-controller` and the classifier.
-- **argus handoff.** How argus learns the classifier passed a PR before it
-  starts its own review.
+- **Reviewer handoff.** How a later reviewer, human or agent, learns the
+  classifier passed a PR before it starts its own review.
 - **Opt-in details.** Beyond the config file: the service account's access
   to a repo, so someone can request it as reviewer and it can push try-out
   branches.