5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	4870c9171e	mesh-cli: build on the SDK that reads the engine's refusal after a failed write, so a caller hears busy, not broken pipe (novox/hq issue 444)	2026-10-11 02:56:55 +02: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	645961a87b	mesh-cli at go/v0.1.9, and the unannounced pull request's number (hq ADR 0272, issue 347) ... - mesh-cli pins the SDK at its tag now that go/v0.1.9 exists, instead of a pseudo-version of the branch it was cut from. - mesh-delivery's stalled line for a head the forge never announced carries the pull request's number, which the controller's condition names in its headline.	2026-10-09 13:41:59 +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