13 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	16b8d8a1ee	Compose as the controller does, so a node's shadow can answer same (issue 1126, C1 C2 C3 C5 C6, T1) ... Seals are reused and compared by slot (resource, field), never across resources; one rule says which resolved config values are laid; a seat path that steps back is owned by the seat it steps back for, whatever the seat order; a folded module of an old-form build is composed from what runs of it; the operator export's file is carried as it runs; a differing resource names its differing JSON paths, found before its bodies are cut, and an answer is fitted to the node's key.	2026-10-28 09:36:36 +01:00
jschoubben	2fd5ffdd62	A node's answer names every module it cannot compose, a folded module of an old-form build is left to the node as it runs, and no store reached says why (issue 1126, the seed's shadow) ... The seed's shadow answers named the first refusal only (ace: baserow's archive, novox: de-spiegel), so each round showed one more. A build that cannot be read or taken in, and a module the composition refuses, are now each composed as a stub and named. A module folded into the node's own composition whose manifest names a build (de-spiegel, nats, photos, systemd-resolved: haves naming a build-... id) runs a build only the controller holds: it is composed as a stub and its resources are carried as the node runs them.	2026-10-27 23:17:05 +01:00
jschoubben	05b6783103	Fold a module no new-form build names into the node's own composition, as the controller does, so a self-composing node keeps the tunnel and the bus (issue 1126) ... mesh-wireguard (built by nobody) and every module a node runs inside its own composition (Node.InOwn, from frombus.InOwn of what it runs) were cut out as skipped: every node's shadow answered differs to the placement seed, and a node composing itself after it would drop their resources. compositions now folds them in place, module taken off, filled paths with them, as mesh-controller's compositionsOf does; a want naming a new-form build still moves one out.	2026-10-27 08:50:26 +01:00
mesh-tools	527840af9b	Give go/facts each machine's grants and bindings, from facts format 2 (issue 1380) ... Machine gains Grants (provision, consumer node, consumer module, local name; no sealed copy) and Bindings (consumer module, provision, provider node, provider module), both omitted when empty. Format moves 1 to 2, because a reader of 1 must refuse a snapshot that says what it cannot read (GrantsFrom names the number); MediaType stays, a reader of 2 reads a snapshot of 1 as having none. Scrubber.Grant and Scrubber.Binding put the machine names under pseudonyms as Pins' are. go/compose's Input.Issued and Node.Bound docs name them as where an assigner fills those from; no logic changes there. Tests: all new ones failed first (the types did not exist); the copied ones are exempt. Unit level 1.19 s (bound 2 s).	2026-10-20 08:25:46 +00:00
mesh-tools	0729556ba3	Read the rest of the mesh and who is on the network with the current manifests: a node's kept build applies only to its own resolution, as the controller keeps a recorded module after reading both (review round 2, item 1). The test asserting the opposite failed first	2026-10-20 07:06:09 +00:00
mesh-tools	3eadff23eb	Take the suffix of internal names from the Input and never the environment: Input.InternalSuffix and a local internal-name helper, so the package doc is true (review round 1, finding 5). The test failed first; the suite is 1257 tests in 1.04 s	2026-10-20 07:02:58 +00:00
mesh-tools	0864ae5e47	Compose a licence key the Input does not carry with a stand-in named foreseen; keep empty only where Keys is given and lacks the holder (review round 1, finding 3). The test failed first	2026-10-20 07:01:50 +00:00
mesh-tools	12319ce9dd	Keep a recorded module at the build a node runs, per node: Node.Kept and Node.KeptBuilds overlay that node's own resolution and the commit it carries, never another node's (review round 1, finding 1; mirrors plan.go keepRecorded and carriedOn). Both tests failed first; the suite is 1251 tests in 1.05 s	2026-10-20 06:59:38 +00:00
mesh-tools	c1ba7bc1ae	Give Input what a declaration's envelope reads: the order it is sent under, whether the engine reads modules, the builds last sent and the builds the mesh holds (issue 1298)	2026-10-20 06:46:54 +00:00
mesh-tools	aecb52c1af	Give Input what the credential half of the rendering reads: the credentials made for consumers, own secrets held, kept core boxes, the bus's user list and memberships, serving keys and certificates (issue 1364)	2026-10-20 06:41:00 +00:00
mesh-tools	084aa4ae75	Give Input what the place half of the rendering reads: taken modules, outward links, attached networks, the engine's contract, built repositories and the operator's export (issue 1363)	2026-10-20 06:33:14 +00:00
mesh-tools	7ba9bcd873	Resolve one node over an Input, its credentials as stand-ins and its settings (issue 1362). Ported from mesh-control 6c2a8d62 planFor. Nothing is made: a pair credential is how it stands (held, to make, only a person's to give, refused), never its value; keepRecorded is left to the caller, who puts the kept manifest in the Catalogue. The bus credential nobody issued and a given own secret under an old key are refused where the controller refuses them, in the rendering (issue 1364).	2026-10-20 06:28:05 +00:00
mesh-tools	cb1b7a6f5d	Compose the private network and the rest of the mesh over a plain Input: Generators and TheRestOfTheMesh (issues 1360, 1361). Ported from mesh-control 6c2a8d62 network.go, plan.go, seat_pass.go. Store-backed tests (aMesh) are rebuilt as Inputs from the same values; the writes they exercised (a placement through overlay place, a seat passed through the store) are Input values or a returned Pass, and the controller-only tests of a failed read or write have no counterpart here. Unit level 1.04 s of 2 s.	2026-10-20 06:22:58 +00:00