0.32.1
Fixed
-
The evidence-coverage pre-flight runs before the machine check.
protocol drive runrefused a map whosellmsteps it could not spawn —metaharnessis not on PATH — before asking whether the map could produce the evidence the plan demands. On any machine without that binary a real coverage gap was never looked for, so the test that guards it passed while guarding nothing. Coverage is decidable from the two documents and says this map can never finish this plan everywhere; the machine check says this machine cannot run it today. The document defect is reported first. An operator whose map has both problems now sees the one that will not go away by installing something. -
0.32.0's
Releaseworkflow failed and published no GitHub Release, on the twodrive_clitests that neededmetaharnessinstalled. Both now assert the same thing on a machine with the binary and one without: the whole gate is green with it hidden.