The SDK conformance test reads the SDK the controller pins, never a desktop's checkout (issue 449) #220

Merged

mesh-admin merged 3 commits from fix/449-the-conformance-test-reads-what-it-carries into main

2026-10-11 09:08:57 +00:00

Author	SHA1	Message	Date
jschoubben	9b6acf0ef5	Read the captured SDK, saying so, when the seat placed no clone beside the check (issue 449) mesh/merge-gate pass: builds mesh-controller → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose) Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery delivered Details The seat runs the running controller's besideRefs, which clones no mesh-sdk until this change has rolled out, so a missing clone failing the test kept this change from ever passing its own check. A follow-up makes it a failure again after the rollout.	2026-10-11 04:20:54 +02:00
jschoubben	4f5fab81fe	Read the SDK fixtures at the pin of the tree under check, not the running controller's (issue 449 review) A pull request moving the SDK passed its check against the old SDK and then failed everywhere once it rolled out. In a merge check the test now reads the clone's history at the tree's own go.mod pin, and holds the captured copy to the clone byte for byte.	2026-10-11 04:19:01 +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