RED-first adversarial guards pinning machine-proven fail-first BEFORE any producer change. They inject a new proveFailFirst option the current producer does not read, so they FAIL against the attestation-greens code (src/prohibition-enforcement.cts:411). This RED is INTENTIONAL — Plans 02-03 wire the prover and turn them green. New tests: - FF-01: attestation + clean pass but no machine proof -> hard-gate (currently RED: producer greens on attestation; actual 'green' vs notStrictEqual 'green') - FF-01 positive: proven-fail-first + clean pass -> green (passes now, pins shape) - FF-04: passes-on-violation (prover could not prove red) -> hard-gate (RED) - FF-04: fails-on-clean even when proven -> hard-gate (passes via runCheck:false) No source edited. 2 new guards RED, 2 positive controls green.
25 KiB
25 KiB