stop provisioning the hive-chat room in the matrix sweep

nix/host-modules/hive-c0re/environment.nix

@@ -170,7 +170,7 @@ in
 }
 // lib.optionalAttrs (config.services.hyperhive.swarm.matrix.apiUrl != null) {
   # Client-server API base hive-c0re uses to provision matrix (register
-  # agent users, create the hive space + chat room, invite members).
+  # agent users, create the hive space, invite members).
   # Supplied by `services.hyperhive.swarm.matrix.apiUrl`, which defaults to
   # the same gateway vhost as HIVE_MATRIX_URL above, over https because it
   # carries the hive's matrix token and may cross the network. Its own

nix/host-modules/hive-matrix-service.nix

@@ -59,8 +59,8 @@ in
       example = "https://matrix.example.com";
       description = ''
         Client-server API base URL **hive-c0re itself** uses to
-        provision matrix (register agent users, create the hive space
-        and chat room, invite members). Distinct from the agent-facing
+        provision matrix (register agent users, create the hive space,
+        invite members). Distinct from the agent-facing
         `services.hyperhive.agent.matrix.url`, which is the gateway vhost handed to
         each agent's `hive-matrix-daemon`.
 

nix/host-modules/hive-matrix.nix

@@ -913,8 +913,8 @@ in
             # the swarm appservice's sender. Its token is read by
             # matrix-ctl and swarm-controller only. Each `@hive-<hive>`
             # stays an ordinary user, because its hive reads its
-            # credential; what it does (the Space, the chat room, the
-            # invites) rides on being the rooms' creator, not on admin.
+            # credential; what it does (the Space and the invites)
+            # rides on being the Space's creator, not on admin.
             #
             # The registration load creates the sender inside
             # `Services::start()`, and `admin_execute` runs after that and