5 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
jochen	7b5c063cd3	The gate's module check notes a seat another module declares, which it was not given (hq issue 364) ... The gate passes only the manifests a change touches, so a module that starts using the operator channel was refused for a declaration it could not see. Over every manifest it stays a refusal.	2026-10-10 03:53:07 +02:00
jochen	14127d4878	Let the module graph decide what a pull request's check runs, in two layers (hq ADR 0237) ... Every pull request the forge announces is mapped onto the mesh's module graph by the merge handler's rule (issue 278): touching a module — or adding one — runs the gate (mesh/merge-gate), its judge chosen by the graph (the controller judges itself, the node-engine by its validator); a repository of the mesh that touches none runs only its own merge-check.sh (mesh/repo-check), a warning when it has none. Nothing is left pending: a repository outside the mesh touching nothing is told so as a pass. The gate moves out of the per-repository scripts into the build seat, so a script is the repository's own tests and declares its toolchain (go or typescript). The controller's manifest names every verb of its seat again (ADR 0132), held by a test.	2026-10-06 22:34:56 +02:00
jschoubben	05d977666a	A setting reaches only what declares it, the mesh places its own files, registration refuses a name ... Three of novox/hq's group-4 leftovers, one branch. Issue 173: a module's settings reached every route it contributed, every database it asked for and every served fact its consumers read — a mail server's site name arrived at the proxy as a route fact. A setting now overrides a key a contribution or served fact declares and adds none; a file still merges any key, and a key nothing takes is named as stray instead of dropped silently. Issue 174: the mesh's own files for a module — its bus credential, its merged config, its bindings — were placed by the definition under /var/lib/mesh/<module>, 232 host paths in 50 definitions. A directory may now say `place: "mesh"` and resolves to <root>/mesh/<module>; a directory beneath a placed one may state its path as `${dir:<id>}/<rest>` and moves with it. The proof test resolves both catalogues and compares: 48 definitions, no path moved. The controller's own manifest is converted here; the catalogue in mesh-catalog. ADR 0155: the installation check moves to registration. `module add` and a build's result both refuse a definition that names an installation, in the check's words, with the way out; the build stays recorded.	2026-09-30 22:29:28 +02:00
jschoubben	2882b5fcb1	A module may invoke tools, and a manifest is checked where it is written ... invokes: a manifest word that becomes exactly the publish grant a person's account gets (ADR 0152), derived by the same composition; refused at parse when it names no tool. module check <file|dir>... runs what registration runs with no store, for a manifest in any repository (hq issue 148).	2026-09-30 16:12:43 +02:00