A provider serves its consumers its own composed names (ADR 0346, issue 624) #306

Merged

mesh-admin merged 3 commits from feat/346-a-provider-serves-its-own-names into main

2026-10-13 19:11:17 +00:00

Author	SHA1	Message	Date
jochen	7a0c219f96	List the provider-elsewhere store test, read a machine's domain as its profile, reuse the settings read once, and refuse a nested own name (hq ADR 0346, review 228) mesh/merge-gate head 7a0c219f961e merged into trunk 332fbaa9b175 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 7a0c219f961e merged into trunk 332fbaa9b175 — pass: its merge-check.sh passed Details mesh/delivery delivered Details	2026-10-13 20:32:51 +02:00
jochen	985423ae61	Say that a provider's own name is not on its consumers' entries (hq ADR 0346)	2026-10-13 20:29:17 +02:00
jochen	cfacda2625	Let a provider serve its consumers its own composed names (hq ADR 0346, issue 624) The forge writes every package tarball at its public name, and its consumers had no source for that name but a second copy kept by hand, though the mesh composes it for the forge's route. A served value may now name the provider's own names; a name its machine does not compose leaves the key out, and the plan says so.	2026-10-13 20:29:17 +02:00