nox works without the controller: each command calls the seat or tool that owns its job (issue 1126) #593

Merged

mesh-tools merged 4 commits from fix/1126-nox into main 2026-11-02 10:56:31 +00:00

Conversation 1 Commits 4 Files Changed 12

+1399 -271

4 Commits

Author	SHA1	Message	Date
jschoubben	63de1f7e0d	nox cleanup delete confirms with the holder's name, as the vault asks ... The vault deletes a retired holder only when confirm repeats its name, so sending confirm "true" could never delete anything. The stand-in console now also says which machine answered as a block of its own, as node-tools does. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 10:47:56 +01:00
jschoubben	9523050a98	nox nodes reads placement with the console's answered-by line after it ... The console appends which machine answered after the JSON, so the nodes table decoded nothing and printed the raw answer; read the first value and keep the trailer. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 10:44:43 +01:00
jschoubben	a3e9f2cc0f	mesh-cli requires the console's endpoint and writes its address ... nox now reaches the mesh through this machine's console, so the module requires mcp-endpoint and writes the bound address to /etc/mesh-cli/console rather than trusting a fixed port. No invokes: mesh-cli has no bus account, and one nothing dials would only be minted. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 10:42:03 +01:00
jschoubben	5cdf8295f3	nox calls the seats that own each job, not the unassigned controller ... The controller nox forwarded every line to is unassigned (issue 1126), so nox answered nothing but enrol open. Each line now calls the seat verb or module tool that owns its job through this machine's console (mesh_call); a line no seat owns says so and names what to use, never failing silently. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 10:41:32 +01:00