messenger hears and asks the condition keeper alone, never the controller (ADR 0564 clause 9)

The three mesh-controller condition-event consumes, the invoke of mesh-controller.conditions, the follow switch
(takeover.go) and its read of mesh-conditions.takeover are gone: the messenger consumes mesh-conditions' events and
reads its open conditions from seat mesh-conditions.conditions at its start. An ask of the keeper is shown on a
condition's message like the controller's was. The manifest test now refuses any controller entry; the event test
refuses the controller's events; the words fixture's action verb names the keeper's. No test added.

(issue 774, 774/S12)

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

modules/messenger/module.json

@@ -74,9 +74,6 @@
     "channel"
   ],
   "consumes": [
-    "mesh-controller.condition-raised",
-    "mesh-controller.condition-changed",
-    "mesh-controller.condition-cleared",
     "mesh-conditions.condition-raised",
     "mesh-conditions.condition-changed",
     "mesh-conditions.condition-cleared",
@@ -92,14 +89,10 @@
     "refused"
   ],
   "invokes": [
-    "seat:mesh-controller.conditions",
     "seat:mesh-conditions.conditions",
     "seat:node-engine.root-free",
     "seat:issue-tracker.tracking"
   ],
-  "reads": [
-    "mesh-conditions.takeover"
-  ],
   "state": [
     "open",
     "sent",