Design 32: the rename window wakes on the node-engine seat's event of ADR 0618, as design 51's old seat name does

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

03-DESIGN/01-to-be/32-what-a-module-declares.md

@@ -516,9 +516,10 @@ value it holds under the old name to the new name in its own state, without the
   module reports applied a build of it that reads the new name. mesh-config hears the status view's `delivered`
   events and, at its start and on each, asks its `node_haves` for every node, away ones included, since `delivered`
   counts only the nodes present (design 47); until then mesh-config answers both names. A node away when the last
-  `delivered` was said should close its window when it returns, with no other delivery; the event that says its
-  return is not yet named, as for the old seat name (design 51), and until it is the window waits on the next
-  `delivered`, tracked on issue 1966. A node holding a window open
+  `delivered` was said closes its window when it returns, with no other delivery: what wakes mesh-config then is the
+  node-engine seat's event for a node's stated manifest-reads, said also on its return, decided in ADR 0618 as for
+  the old seat name (design 51; the event's family is filled in once it is proposed), never a watch of the
+  node-engine's have state (ADR 0596). A node holding a window open
   for seven days is mesh-config's finding naming the node, cleared when the window closes; `config_rename_close`
   drops a node from a window by hand, recorded as a hand act.
 - **The checker asks the seat, never the module.** The seat `mesh-config` gains the optional verb `renames` (the