mirror of
https://github.com/bdbrown4/peltier.io.git
synced 2026-11-07 10:58:28 +00:00
Adds the diff-test CLI ('just gates <target>'): loads
targets/<name>/target.toml (new [corpus] section: manifest, root,
golden_sha256; commands now repo-root-relative), verifies the corpus
manifest FIRST and refuses to run any gate on mismatch, then runs the
upstream test suite and golden replay (stdout sha256 vs pinned hash).
Differential fuzz and sanitizers remain per-attempt manual steps in
Phase 1 and are reported as skipped-with-reason; all-skipped is not a
pass.
Verified end-to-end on both vendored targets (comrak: 1 pinned file,
848 tests, golden PASS; tokei: 545 pinned files, 250 tests, golden
PASS) and the refusal path (tampered corpus -> 'HASH MISMATCH ...
refusing to run' before any gate executes).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EcKPWQ3MQD4NdEHwar96u2
targets/
One directory per optimization target. This is the only agent-writable path in the repository (SPEC §10); everything else is trust layer.
Layout
targets/<name>/
target.toml # upstream repo URL, pinned commit, build & bench commands
equivalence.toml # optional; absent = byte-identical required (SPEC §3.2)
workspace/ # agent's checkout — patches land here via harness git-apply
Selection criteria (SPEC §6): CPU-bound (>70% user time), meaningful test suite, scriptable workload, permissive license, active but not hyper-optimized, builds cleanly in a container. Good hunting: codecs, parsers, serializers, image processing, compression, static-site generators, linters.
equivalence.toml
Default (no file) is byte-identical outputs. FP-producing targets may declare an explicit tolerance policy:
mode = "fp-tolerance"
abs = 1e-9 # max absolute difference per numeric value
rel = 1e-6 # max relative difference per numeric value
Declaring a tolerance covers output comparison only; FP flag changes still route to needs-human-review (SPEC §8).