3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	eb72075104	Judge tests that read another repository against what the check clones, never the desktop's checkout (issue 432) ... Tests that read ../../../mesh-catalog or ../../../mesh-host gave a verdict that depended on what sat beside the checkout: a stale or dirty sibling failed them on a desktop, and a missing one skipped them unseen. They now read the clone the build seat puts in MESH_CHECK_BESIDE, failing when it is absent there, and elsewhere a copy captured at a named commit. The skip had hidden that the builder test read a module retired by ADR 0190. The systemd reading test no longer counts the machine's own environment.d.	2026-10-11 02:55:04 +02:00
jschoubben	05ff6065d0	Event names are checked now, per manifest and across the catalogue ... Issue 127 stood because nothing compared the two halves. Every manifest was well-formed on its own and every derivation correct on its own, and no cross-module subscription in the mesh matched anything — a subscription that matches nothing is not an error, it is silence. Two checks, because the mistake is possible at two scales. Per manifest: an event is a local name, and `module.` is refused with the name to write instead. A module emitting under what reads as another module's name is refused too, pointing at the seat, where a name outlives whoever holds it. Across the catalogue: where a consumed event's emitter is present, it must emit that event. It cannot demand a live emitter for everything — a module lives in its own repository and may be installed long before the one whose events it wants — so the rule is narrower and still catches this. It found two real dangling subscriptions the moment it ran. Wildcards were undecided and two manifests needed them: `*` is one name and `**` is the rest, spelled the mesh's way and derived to `>` here and `#` on the old bus. A manifest naming either would stop being true when the wire changed, which is the whole reason names are local. And the field documentation taught the old form, examples included — which is why the drift was uniform across 37 manifests rather than scattered. Nobody was guessing; everybody followed the comment.	2026-09-27 14:43:16 +02:00
jschoubben	bf82805cfd	A manifest holds no subject, checked across all 72 ... Design 29 §1's load-bearing rule: a module names its events, tools and seats locally and the mesh derives the subject, so reorganising the subject space leaves every manifest correct. It held by construction, and a rule held by construction is one a later field breaks quietly.	2026-09-26 23:34:42 +02:00