archetype flows on the board list the agents the router sends to, and the docs say a switch-off key outlives its flow

docs/2-handbook/swarm/archetypes.md

@@ -163,7 +163,9 @@ within about 10 seconds, and the card has no `edit` button.
   flow can also request a review, which an archetype's flow can't. Switch the
   archetype's flow off to replace it with your copy.
 - A key for a flow or agent that no longer exists stays in the list and does nothing, so
-  editing an archetype never breaks the stored flows.
+  editing an archetype never breaks the stored flows. The key stays
+  after its flow goes: a later flow with the same archetype and id comes up
+  already switched off; switch it on from its card.
 
 ## How the list stays current
 

docs/4-implementation/swarm/notify-router.md

@@ -303,7 +303,7 @@ it refuses any id that's no built-in.
 `[{archetype, key, flow, members}]`, one per enabled archetype flow that passes
 the archetype check and has an agent, with the flow as the archetype declares it
 (a `todo` to `"members"`). The controller reads the archetype records and the
-`agent-archetype` keys itself; a read that fails leaves the list empty and the
+`agent-archetype` keys itself, and lists as members the agents the router sends to: those with a key that are in the agent-status roster. A read that fails leaves the list empty and the
 document still comes back. The page draws a card for each, with the `on` switch (the
 key), a checkbox per member (the key with `@<agent>`) and `duplicate`, which
 opens the editor on `?from=<key>`. The copy replaces `"members"` with the one