5 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
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	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	57d852e7da	Test the whole-node composition: Compose accepted by the validator, refused manifests as problems, an unresolvable set as an error, determinism, foreseen outputs, the envelope's order and builds, adoption, the overflow refusal (issue 1298)	2026-10-20 06:49:28 +00:00