6 Commits

Include renames

Author	SHA1	Message	Date
evangelostsak	81b2af9abd	refactor: drop rationale and narration from inventories/examples/wireguard-three-meshes/wireguard.yml	2026-10-16 19:10:00 +02:00
evangelostsak	a87c56c569	docs(examples): show where the mesh values go in host_vars	2026-10-14 15:03:41 +02:00
evangelostsak	f3e4eae919	refactor(examples): remove the separate three-mesh declarations	2026-10-14 15:03:41 +02:00
evangelostsak	1cd743532b	feat(examples): the three-mesh layout as inventory values	2026-10-14 15:03:41 +02:00
evangelostsak	a992b5d1a2	docs(examples): explain the primary mesh and how to test the example ... Covers declaration order, the local and CI commands, and that the lab is stricter than this inventory: its NFS server is a spoke of beta and gamma.	2026-10-14 11:23:22 +02:00
evangelostsak	b777b65e84	test(mesh): hold the planning guarantees at any mesh count ... The guarantees were asserted against the declared swarm and data pair, so they proved two meshes work rather than that the planner works. A deployment declares its own, and the review asks for any number of them with the nodes arranged however the client wants. The same invariants now run over generated topologies: one to eight meshes, three arrangements each, hosts dealt out so some belong to several meshes and some to none. 2247 subtests, four seconds, and the planner needed no change to pass them.	2026-10-13 19:36:43 +02:00