The node-engine trusts the vault alone, loads the grants part's user list alone and applies only its own compositions (issue 1126) #196

Merged

mesh-tools merged 2 commits from fix/1126-gates-host into main 2026-11-02 09:51:16 +00:00

Conversation 1 Commits 2 Files Changed 13

+221 -1145

2 Commits

Author	SHA1	Message	Date
jschoubben	38d666f223	Apply only the node's own compositions, never the controller's ... The controller ended by its unassignment, so a node that falls back to the compositions in its bucket follows what nobody writes (issue 1126, A7). The node agent now always runs its own composer: without a placement key it composes nothing and keeps what runs, a placement it cannot watch stops the agent and is said, and a candidate taking its placement away is refused instead of answered as a return to the controller. The start-time placement read, the end-when-placed watchers and the returning answer go, with their tests and the three integration tests of the controller-composed path. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 10:40:50 +01:00
jschoubben	5cfc4ff4a7	Trust the vault's key alone and write the grants part's user list alone ... The controller ended by its unassignment and its lease is never handed, so the engine's lease gate kept trusting the controller's key and the bus node kept the controller's list as a fallback nobody writes (issue 1126, A6). The engine now trusts no controller signature, its hand-over line names the node seat's hand-over, and the user-list follower writes only the grants part's list: a key unreadable or deleted keeps the list loaded, and with no key heard nothing is written. Compositions in the node's bucket name the file's place alone. The guard no longer asks for the controller's user. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 10:37:27 +01:00