gates: close the audit findings — enforce the gates the docs claimed

An adversarial audit found the enforcement story ahead of the code: gates
that were documented as hard gates were advisory, manual, or absent, and
several human-facing claims outran the machine record. This makes the
claims true.

High findings

- Differential fuzz was documentation, not enforcement: verdict hardcoded
  fuzz_iters=0 and diff-test hardcoded the gate to Skipped, while the case
  studies claimed 10k-iteration fuzz on the same wins. Fuzz is now a real
  pipeline gate (strict FUZZ-RESULT contract, executed count recorded), and
  it is inherently baseline-vs-candidate, so it runs on the accept path and
  reports Skipped in the standalone `just gates` flow. New hard rule: a
  machine `accepted` verdict is impossible unless the fuzz gate actually
  passed — otherwise it caps at needs-human-review.
- The agent's system prompt claimed FP/concurrency/unsafe patches were
  "routed to human review automatically". No such mechanism existed. Added
  a conservative lexical risk classifier (crates/verdict/src/risk.rs) that
  forces needs-human-review on any would-be accept carrying those signals;
  fp-tolerance equivalence always signals.
- The local verdict path ran agent-influenced code unsandboxed. It now runs
  under scripts/no-net.sh (network namespace) and fails closed. Upstream
  test suites are hash-verified against corpora/<t>/TESTSUITE.sha256 when
  present (scripts/pin-testsuite.sh generates them).

Also fixed, found while fixing the above

- The pipeline script's `set -e` was inert (brace group as the left operand
  of `&&`), so a failing candidate build did not abort the run and verdict
  could bench a stale binary. Now a scoped subshell whose status is branched
  on at top level.
- A wrapper that exits before exec'ing (no-net.sh refusing, bad wrapper path)
  stranded RUNNING.lock and left read_verdict polling forever. Failure
  accounting now lives outside the wrapper.
- harnessd's patch allowlist ignored git rename/copy headers and --no-prefix
  diffs; the rename-escape case is now a committed regression test.
- The workspace did not compile on Windows (ungated Unix APIs). cfg-gated;
  71 portable tests now run on both platforms.
- pin-check regenerated the corpus manifest instead of verifying it; it is
  now verify-only, with a deliberate `just pin-corpus` to re-pin.
- Max RSS is captured per run on Unix; PMU counters are opt-in diagnostics
  (compare --perf-stat), never part of the accept decision.

Docs now match the code, including what is NOT yet enforced: no target ships
a TESTSUITE.sha256 pin, no target declares [build].tsan, and matmul is not
wired to the fp-tolerance gate — each is stated as mechanized-but-inert
rather than done. Corrected the stale "33 ledger rows" (34), the playbook's
class-3 cJSON win (rejected), adversarial-review.md's sanitizer-separation
claim (five accepted rows carry sanitizers_clean=false), the unsupported
"40,000 requests" figure, and the blanket "historical rows record
fuzz_iters=0" (8 of 10; phase0-tokei-002/-003 record 4,332).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

results/phase3/01-tokei-algorithmic-rust.md

@@ -62,3 +62,12 @@ increments, all on the same 40%-of-runtime function — and one honest
 rejection in between (`phase2-tokei-009`, a real +5.7% median whose
 noisy CI lower bound of +0.2% could not clear the bar, so it does not
 count).
+
+---
+
+> **Note (2026-07-13).** The 10,000-input differential fuzz cited above
+> ran **out-of-band** (`scripts/diff-fuzz-tokei.py`, per-attempt), not
+> inside the verdict pipeline — so these ledger rows record
+> `fuzz_iters=0` in their machine record. The fuzz gate is now
+> pipeline-integrated; rows written after this date record the
+> iteration count actually executed.

results/phase3/04-cjson-c-target.md

@@ -84,3 +84,12 @@ about the trust story is Rust-specific. The cheapest safe lever (skip a
 per-number allocation) wasn't enough; the algorithmic lever (stop doing a
 redundant heavyweight parse) was — and the pipeline proved it the same
 way it proves everything else.
+
+---
+
+> **Note (2026-07-13).** The 10,000-input differential fuzz cited above
+> ran **out-of-band** (`scripts/diff-fuzz-cjson.py`, per-attempt), not
+> inside the verdict pipeline — so the `phase3-cjson-002` ledger row
+> records `fuzz_iters=0` in its machine record. The fuzz gate is now
+> pipeline-integrated; rows written after this date record the
+> iteration count actually executed.

results/phase3/README.md

@@ -66,3 +66,13 @@ fuzz, and sanitizers. Every rejection is a real mechanism that simply
 didn't clear the 2% CI-lower-bound bar — and it is in the ledger too,
 because a rejection is a complete, valid outcome. Nothing shipped that
 the pipeline couldn't prove.
+
+> **Note (2026-07-13).** "Every win survived … a 10k-input differential
+> fuzz, and sanitizers" is true of the **evidence**, not of the machine
+> record at the time: through Phase 5 the fuzz ran **out-of-band**
+> (`scripts/diff-fuzz-<target>.py`, per-attempt) and the Phase 3 rows
+> therefore carry `fuzz_iters=0`. The fuzz gate is now integrated into the
+> accept path, where a passed fuzz gate is a **precondition** for a machine
+> `accepted` verdict; rows written after this date record the iteration
+> count actually executed. See the per-case-study notes in
+> `01-tokei-algorithmic-rust.md` and `04-cjson-c-target.md`.