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
2026-11-05 22:29:07 +01:00
parent 2dc9e07e88
commit c9d8950fd0
109 changed files with 682 additions and 681 deletions
@@ -3,7 +3,7 @@ package main
 // Where disk-load learns the data items it measures (novox/hq ADR 0577 clause 2): the node-engine's state data
 // (engineDataBucket), one key `<node>.<module>` per module placed on this node that declares data items, as the
 // engine composed them. disk-load watches its own node's keys and composes nothing: it reads no resolved values, no
-// manifests and no placement, so a manifest its mesh-sdk cannot judge never silences it, and a round reads one watched
+// manifests and no assignments, so a manifest its mesh-sdk cannot judge never silences it, and a round reads one watched
 // map instead of several hundred keys over the tunnel (issue 1955).

 import (