7 Commits

Include renames

Author	SHA1	Message	Date
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
jschoubben	9249ca7b57	mesh-cli: nox enrol open opens a sealed enrolment token locally with the operator's private key ... The seat mesh-enrolment's tokens answers the token sealed to the operator key; the operator opens it at their own terminal. The subcommand reads the sealed token on standard input and the private key from a file, prints the token text a joining machine takes, asks nothing of the node-engine's socket, and says the token is not sealed to a wrong key (ADR 0587 §6, §8). New: one table-style test function; mesh-cli had 6, so none was merged or deleted. (issue 774, 774/S51) Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 01:42:19 +01:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00
jschoubben	f3dcb9dc5a	mesh-cli: carry what a pipe or a file gives standard input with the line, at most 64 KiB ... So a secret reaches the controller's terminal without standing on a command line: mesh-cli secret accept <node> <module> <name> --from - < file. A terminal is never read, more than the bound is refused before anything is asked, and nothing carried is printed. mesh-sdk moves to f047d0a.	2026-10-09 16:50:46 +02:00
jochen	6f1c559d93	mesh-cli: say an outcome not known, and hold the module to placing one file (review of hq ADR 0272) ... A line whose answer did not come in time is said as possibly run, with its call, never as nothing having run. A test holds the module to one archive resource unpacking one compiled Go bundle into /usr/local/bin. The README says the MESH_VERB refusal is a courtesy and the controller is the gate. SDK pinned at the go/cli branch's newest commit until go/v0.1.9.	2026-10-09 12:49:14 +02:00
jochen	2594a24b35	mesh-cli: the operator's command on every node, nox in zsh (hq ADR 0272) ... The records send the operator to "the controller's terminal", and on the control-node nothing answered (hq issue 343). mesh-cli is a module of its own, assigned to every node and built from its own directory: its program is unpacked into /usr/local/bin by an archive resource (one file, no link, no copy), and its zsh contribution makes nox its alias. It holds no credential: it asks the node-engine on its machine over the SDK's go/cli socket, and prints the controller's answer with its exit. The agent module's refusals and README, and the route adapter's README, now name `mesh-cli settings set …` on the control-node instead of a mesh-controller command nobody could type; a settings file is passed inline, since a path would be read where the controller runs.	2026-10-09 12:11:21 +02:00