mirror of
https://github.com/bdbrown4/peltier.io.git
synced 2026-11-07 10:58:28 +00:00
benbrownandClaude Opus 4.8
899d55f4b6
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>
37 lines
1.8 KiB
TOML
37 lines
1.8 KiB
TOML
# tokei — source-code statistics tool (Rust)
|
|
# Selection vs SPEC §6: CPU-bound line/language analysis (83% user time,
|
|
# single-threaded mode); upstream test suite; scriptable deterministic
|
|
# workload; MIT OR Apache-2.0; active, no dedicated perf team.
|
|
|
|
[source]
|
|
repo = "https://github.com/XAMPPRocky/tokei.git"
|
|
commit = "fa44e5194060305576514d59b850353643afbfc8" # v14.0.0
|
|
license = "MIT OR Apache-2.0"
|
|
|
|
[build]
|
|
baseline = "CARGO_TARGET_DIR={out} cargo build --release --manifest-path targets/tokei/workspace/Cargo.toml"
|
|
binary = "{out}/release/tokei"
|
|
sanitizer = "CARGO_TARGET_DIR={out} RUSTFLAGS='-Zsanitizer=address' cargo +nightly build --target x86_64-unknown-linux-gnu --manifest-path targets/tokei/workspace/Cargo.toml"
|
|
sanitizer_binary = "{out}/x86_64-unknown-linux-gnu/debug/tokei"
|
|
|
|
[bench]
|
|
# Single rayon thread: measurement first (SPEC conventions); the
|
|
# multi-thread mode is a playbook class-7 concern, not the baseline.
|
|
command = "RAYON_NUM_THREADS=1 {binary} --sort code corpora/tokei/input > /dev/null"
|
|
workload = "8 replicas of pinned progit + comrak/src trees, 221 MB, 4360 files, single rayon thread"
|
|
|
|
[gates]
|
|
tests = "cargo test --release --manifest-path targets/tokei/workspace/Cargo.toml"
|
|
golden = "RAYON_NUM_THREADS=1 {binary} --sort code corpora/tokei/input"
|
|
# Differential fuzz, pipeline-integrated: diff-test substitutes {iters},
|
|
# {baseline} (the pristine binary the accept path rebuilds) and {candidate},
|
|
# then parses the script's final FUZZ-RESULT line. The harness owns where the
|
|
# pristine build lands, so the script takes the baseline from argv and never
|
|
# hardcodes a path; paths may be repo-root-relative or absolute.
|
|
fuzz = "python3 scripts/diff-fuzz-tokei.py targets/tokei/fuzz-work {iters} {baseline} {candidate}"
|
|
|
|
[corpus]
|
|
manifest = "corpora/tokei/MANIFEST.sha256"
|
|
root = "corpora/tokei/input/copy1"
|
|
golden_sha256 = "corpora/tokei/GOLDEN.sha256"
|