4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	6bdf958cef	failurekit looks for the conformance kit at the build runner's package, where it moved (ADR 0593 §1) ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 18:35:48 +01:00
jochen	3d42988afa	Hold every build module to ending what a previous process left running (issue 1890) ... A replaced mesh-build-go left a check ask's step running and its start sweep spared it (issue 1890, note 21). mesh-build-go, mesh-build-node and mesh-build-image pin mesh-sdk 981a35b5, whose steps name their owner and whose sweep ends another owner's at once; each runs the sweep through one method that main calls and that its test runs through the conformance kit's left-running case. The failurekit check now refuses a build module whose tests do not run that case, test step or not.	2026-10-27 01:22:13 +01:00
jschoubben	e8a953818c	Merge main into fix/1901-failure-contract: pin mesh-sdk a2759ec (the group's sdk head), the failure kit check's marker lists what it reads (issue 1936), and the registry test's password can no longer match a random workspace name (issue 1901)	2026-10-27 00:39:35 +01:00
jschoubben	175b2cd791	Build modules report failed tests through mesh-sdk's failure contract and run its conformance kit (issue 1901) ... mesh-build-node kept the first fifteen lines of node --test's output, so a passing line of the first file stood for the failure. Both build modules now parse through the SDK (go test -json, node --test's TAP report written to a file, the type-check and go vet as console failures), name themselves in the result, and run the SDK's captured cases; the catalogue check failurekit refuses a node-build-* module with a test step whose tests do not run the kit.	2026-10-26 19:48:39 +01:00