Name no controller verb in hints and drop its handover and paging reads, since the controller ended (issue 1126 B19)

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

README.md

@@ -45,7 +45,7 @@ MESH_OPERATOR_ACCOUNT   whose machine this is, and MESH_OPERATOR_HOME where thei
 MESH_BROKER_URL         a plain URL instead of the credential, for the bootstrap case
 ```
 
-`node dist/main.js`. On a node the controller composes the variables and the host supervises the
+`node dist/main.js`. On a node the mesh composes the variables and the node-engine supervises the
 process like any other host-side workload (novox/hq to-be 38). As `node-tools` the same process is
 the console: MCP on `127.0.0.1:4270` (or `MESH_CONSOLE_LISTEN`).
 
@@ -66,14 +66,14 @@ answer took, its size in bytes, how many modules and tools it announced, whether
 fit the bus, when it was last heard — and who was expected and not heard).
 
 `mesh_search` also finds a tool by the shell command it replaces (novox/hq ADR 0245): each seat verb and
-module tool says what it replaces in the controller's records (`replaces`, read from the controller's
+module tool says what it replaces in the indexer's records (`replaces`, read from its
 `tools` and `modules` answers), so `journalctl -u x`, `systemctl status x` or `docker ps` puts the verb
 for it first, and says the command it matched as `instead_of`. A word also matches through a short table
 of the words agents use for the mesh's (`logs` finds the journal). Best first: a replaced command, then
 words in a name or a replaced command, then words in a description; seats before modules on a tie.
 
 Discovery asks the bus (ADR 0197): every runtime answers the NATS services protocol's `$SRV.PING` and
-`$SRV.INFO` with what it serves at that moment, and the console reads where the controller's records
+`$SRV.INFO` with what it serves at that moment, and the console reads where the placement seat's records
 place each module. The console waits at least 750 ms, and up to 5 s for every runtime that answered
 PING to send what it serves — a large runtime's answer crossing the bus to a broker on another machine
 can arrive well after the rest. A runtime that said it is there and did not say what it serves, or