4 Commits

Include renames

Author	SHA1	Message	Date
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
jochen	57d524f4ef	Fold public-acme into route-proxy; drop dhcpcd and cloudflare-dns (hq ADR 0226) ... public-acme ran nothing and had one consumer. The proxy now states the issuer itself, byte for byte what the binding rendered, so its account directory and every certificate stay put. dhcpcd and cloudflare-dns are assigned nowhere and nothing requires what they provide.	2026-10-06 14:59:43 +02:00
jochen	b2e39eb2cd	route-adapter: write a body limit as the predecessor's buffering middleware ... The adapter skips what its one file shape cannot say. A body limit is the exception: the predecessor has a buffering middleware and served its own registry name with exactly it, so this is written rather than skipped, named after the router so the two halves cannot drift. A limit that is not a whole positive number of bytes takes the route with it. Written without the limit, the predecessor would carry what the module said not to carry and this module would report success. Silence stays silence — no middleware, the predecessor's default.	2026-09-26 16:01:23 +02:00
jschoubben	bd5b349a0d	route-adapter: provide route by writing into the predecessor's proxy (hq ADR 0104) ... A node being adopted cannot take a web module: every module reachable by name requires route, the mesh's only provider of it binds the two public ports, and the predecessor's proxy holds them and serves every public name there. Stopping the predecessor to break the circle darkens every name at once, with every certificate to re-obtain in the same window. So this answers the same provision without binding anything. It provides route and receives the same contributions file, and writes each contribution as one route file where the predecessor's file provider reads, naming the predecessor's own certificate resolver so no certificate is asked for. It removes a file it wrote when its contribution goes and never touches a file it did not write — the name and a marker inside both have to say it is the mesh's. A step, not a daemon: run-once, re-run by restart-on over the received file and the settings. The predecessor's dynamic directory is a node setting, because it is a fact about one machine. Migration scaffolding with a stated end: assigned only on an adopted node, deleted when the predecessor's proxy retires.	2026-09-23 00:11:21 +02:00