The gate raises the mesh as it is, and a baseline that does not compose is an error; check-here runs a check as the seat does (hq issues 285, 286) #104

Merged

mesh-admin merged 2 commits from fix/gate-baseline-composes into main 2026-10-06 23:59:43 +00:00

Conversation 3 Commits 2 Files Changed 12

+641 -31

2 Commits

Author	SHA1	Message	Date
jochen	0d2fd2c5bb	Remove everything a check run by hand leaves, the toolchain's files under its HOME too	2026-10-07 01:48:37 +02:00
jochen	a011743c69	Raise the mesh as it is in the gate, call a baseline that does not compose an error, and let a check run by hand as the seat runs it ... The gate composed 0 of 4 machines with the change and without, and passed every change: the store it raised held each module's bus credential but no account for it (issue 203's refusal), no outward links (so no filter could be composed), and refused settings the mesh holds. Now the account is minted with its credential, the facts carry each machine's outward links (a stand-in for an older snapshot), the mesh's layers are kept as held, and a withheld path keeps a path's shape. A machine the mesh composes that the gate cannot raise makes the verdict an error, never a pass; the verdict alone is on stdout. A merge-check.sh that passed on an agent's machine failed on the build seat: a newer gofmt, siblings at a feature branch, another user. `mesh-controller check-here` runs builder.Check with the ask the controller would make, from facts that now name the toolchains and the refs cloned beside; a failed script is said by what failed. (novox/hq issues 282, 283)	2026-10-07 01:33:18 +02:00