5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	24f5ee81bd	cli: after a failed write take only a refusal, since nothing can have run, and pin that the read keeps the ask's deadline (hq issue 444)	2026-10-11 02:49:17 +02:00
jschoubben	b4900f52b8	cli: read the engine's answer after a failed request write, so a refusal is not lost as a broken pipe (hq issue 444)	2026-10-11 02:43:54 +02:00
jschoubben	f047d0a4a9	go/cli: carry mesh-cli's standard input with its line, bounded at 64 KiB, for the controller's terminal alone ... A secret given at the terminal (secret accept … --from -) has no way through mesh-cli today: the controller runs every line with no standard input. The request now carries it, refused over 64 KiB by mesh-cli and by the reader alike, and MaxRequest grows by what base64 makes of that bound.	2026-10-09 16:33:44 +02:00
jochen	a5a040c904	go/cli: an outcome not known is not a refusal; the Go binding is checked in the Go toolchain ... Review of hq ADR 0272: a line whose answer did not come in time may have run, and saying "nothing ran" there is a lie. Answer.Unknown and NotKnown say it may have run and name the call to look at. The SDK's repo-check ran in the TypeScript toolchain only and said "NOT TESTED HERE: go/". go/merge-check.sh now runs the Go binding in the Go toolchain, declared by the root check (mesh-check-also), as the lab does. Released as go/v0.1.9 (go/v0.1.8 is mesh-sdk #12's).	2026-10-09 12:37:48 +02:00
jochen	bfe82315f4	go/cli: the local protocol mesh-cli speaks to the node-engine (hq ADR 0272) ... mesh-cli holds no credential: it asks the node-engine on its own machine over a socket, and the node-engine reads the account from the kernel. The socket's path, the request and the answer are shared by the program and the node-engine, so they live here once (ADR 0039: a local protocol a module's program speaks to its runtime). The bus request the node-engine then makes is the transport's, and stays out of the SDK.	2026-10-09 12:03:14 +02:00