8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	bd7731f358	Count a machine that does not resolve and holds a place as on the network for its name and the mesh's sources too (issue 1833) ... The tunnel kept such a machine while the names and the packet filter's sources from the mesh, read from their own unchecked resolve, dropped it when that pass refused it too (a seat claimed twice): every other machine was sent the hub as a peer without its name or its address. onTheNetwork keeps it by the same rule as network().	2026-10-22 15:26:48 +02:00
jschoubben	c154bdedd3	Keep a machine that does not resolve on the private network at its place, so one machine's modules refuse only its own declaration (issue 1833) ... A machine whose own set could not be resolved was left off the private network; when it was the hub, the network could not be composed and every machine's declaration failed. Its placement (key and address) is its last good place and does not change when its modules fail, so it stays on the network and only its own declaration is refused. A refused machine with no place is left off, and a network that cannot be composed from what remains still fails.	2026-10-22 15:03:17 +02: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	28d4b9eb0d	Return the lines the composition found on the way (a node not counted as on the network) in Rendered.Said and Declared.Said (review round 1, finding 6). The test failed first; the suite is 1258 tests in 1.05 s	2026-10-20 07:03:36 +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	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	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