keep the operator list under one key and read it with one direct get

The agent read the operator-profiles bucket with a keys() listing, an
ordered consumer whose grant (STREAM.INFO, CONSUMER.CREATE) and flow-control
reply had never run against a permissioned queue. The controller now writes
the whole list as one JSON array under one key, only when it changed, and
the agent reads it with one DIRECT.GET the way agent_inference::read_own
reads its key. The agent grant shrinks to that one subject.

docs/turn-loop/claude-invocation.md

@@ -263,8 +263,8 @@ needs to `chown` a bind mount), once at startup:
   shape for the swarm), and `{operators}`: a paragraph listing the
   swarm's operators with the pronouns from each one's forge profile,
   for example `Operators: mara (she/her), sol.`. The harness reads
-  them from the `operator-profiles` KV bucket, which
-  `swarm-controller` writes. The harness waits up to five seconds for
+  them with one direct get on the one key of the `operator-profiles`
+  KV bucket, which `swarm-controller` writes. The harness waits up to five seconds for
   them. When the bucket is empty or doesn't answer in time,
   `{operators}` is empty and the prompt names no operator. Either way
   the template tells agents to say "the operator" in third person. A