mesh-controller

8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	201bd28278	Keep a walk's withheld modules on its record, name every machine a stopped send reached, and list the stop's store tests (review of #232 ) mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without … Details mesh/repo-check fail: its merge-check.sh failed: 3 store test(s) listed in testdata/store-tests did not run and pass against the store Details mesh/delivery-group group feat/459-a-stop-re-walks-the-others rejected: a member's own check failed Details mesh/delivery superseded: a newer head of the same pull request Details	2026-10-11 20:25:20 +02:00
jschoubben	731143f5b9	Fail the repo check when a listed store test did not run against the store (hq issue 459) mesh/merge-gate pass: builds build-agent → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose) Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details mesh/delivery covered after its stop: a later merge that contains it was delivered: novox/mesh-controller@e2801773c300 (merged as ece37596 into main, wal… Details A test that needs the store skips without one, and a skip passes unseen, so a change's store tests could pass the check without ever running. Tests named in testdata/store-tests must each run and pass, said by name.	2026-10-11 20:22:56 +02:00
mesh-admin	315cbd1f54	Merge pull request 'Issue 496: a definition's resolved directory and file paths are judged by the node-engine's rules where the definition is judged' (#228 ) from fix/496-a-resolved-path-is-judged into main	2026-10-11 17:49:40 +00:00
jschoubben	8115f1ac42	Judge a definition's resolved paths where the definition is judged, by the node-engine's own rules, so a refusal never freezes a machine (review of #228 , issue 496) mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without … Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery delivered Details	2026-10-11 18:59:07 +02:00
jschoubben	72fde0ee1a	Capture the SDK's conformance fixtures at the commit the node-engine's pin moved it to (hq issue 449's rule)	2026-10-11 11:30:16 +02:00
jschoubben	4632b6a508	Judge the SDK conformance fixtures against the SDK the controller pins, never a desktop's checkout (issue 449) A check clones mesh-sdk beside the controller at the commit go.mod pins; elsewhere the test reads a copy captured at that commit, held to go.mod. A missing clone fails instead of skipping.	2026-10-11 04:19:01 +02:00
jschoubben	68fbd99e89	Say how a check's clones are chosen and what the captured copy carries (issue 432 review) mesh/merge-gate pass: the change touches no module of the mesh's graph Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery delivered Details	2026-10-11 03:00:28 +02:00
jschoubben	eb72075104	Judge tests that read another repository against what the check clones, never the desktop's checkout (issue 432) mesh/merge-gate pass: the change touches no module of the mesh's graph Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery superseded: a newer head of the same pull request Details 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