an archetype carries its own notification-router flows for its agents

ArchetypeMeta gets flows, checked when the controller stores the record: every todo must go to the new members recipient, which the router expands to the agents of the archetype. The operator's flows document refuses members. The router reads the archetype records and each roster agent's archetype key, and its NATS grant gains read on both buckets.

swarm-notify-router/Cargo.toml

@@ -28,6 +28,9 @@ serde_json.workspace = true
 swarm-queue-client = { workspace = true, features = [
   "forge-events",
   "router-todo",
+  # `archetypes::open` and `agent_archetype::read`, for the flows archetypes carry.
+  "kv",
+  "agent-archetype",
 ] }
 # Its queue client secret, read with its own store leaf.
 swarm-secret-client = { workspace = true, features = ["otel"] }