Every module follows the assigner's new places: the contracts' go/ path, mesh-wants in the delivery contracts, the state and tool assignments (issue 1966)

The legacy key form placement.<node> is gone from the client, so the readers and their fixtures lose it. The check noplacement
now also refuses the assigner's retired names in a manifest.

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

modules/mesh-cli/README.md

@@ -33,7 +33,7 @@ module node-tools serves on loopback (novox/hq ADR 0152: whoever is on the machi
 puts the call on the bus, as every agent session on the machine does. The console's address is read from
 `/etc/mesh-cli/console`, or `MESH_CONSOLE` when set, or node-tools' declared port when the file is not there yet.
 
-- **Who judges.** The seat that owns the job: a change of placement is a proposal the operator approves
+- **Who judges.** The seat that owns the job: a change of assignments is a proposal the operator approves
   (`mesh-module-assigner.propose`), a config value is set with its why (`mesh-config.config`), a silence or a hand act is
   recorded as one. Until novox/hq issue 1126 the controller ran these lines and judged the account (ADR 0272); with
   the controller unassigned, that judgement went with it.