fix(client): rotating a group key asks nothing

Rotation narrows rather than widens: members still connected receive the
new key, and nothing already shared changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md
index 51c7eb7..2419916 100644
--- a/docs/MESHBAY_DESIGN.md
+++ b/docs/MESHBAY_DESIGN.md
@@ -2441,11 +2441,11 @@ What running it establishes, and what each fact costs:
   process checks the arguments — ids are ids, names are encoded — builds the
   request and adds the node's token. `node:start` writes the hub this application
   is signed in to and a username the hub would register, never a value the page
-  supplies verbatim. **What widens what the node shares or admits, or replaces its
-  group key, is confirmed by a dialog the main process draws**: hosting a group or
-  sharing a folder with a folder not chosen in the native folder picker (one chosen
-  there is its own confirmation, so the ordinary path asks nothing), rotating the key,
-  clearing the denylist, and pointing the node at another account. The words come
+  supplies verbatim. **What widens what the node shares or admits is
+  confirmed by a dialog the main process draws**: hosting a group or sharing a
+  folder with a folder not chosen in the native folder picker (one chosen there is
+  its own confirmation, so the ordinary path asks nothing), clearing the denylist,
+  and pointing the node at another account. The words come
   from the interface's catalogues, read by the main process; the page sets the
   language and nothing else. An in-page confirmation is one a script in the page
   can answer for itself. **Every channel answers only the packaged page's top-level