mirror of
https://github.com/StewBC/cc65-Chess.git
synced 2026-10-25 01:02:25 +00:00
Stefan WesselsandClaude Opus 5
cd9bc15af6
The gauntlet needed two absolute paths on the command line, which made every recorded invocation specific to one machine. It now looks in tools/, then on PATH, then in the usual package-manager prefixes, and --which reports what it found. Engine and book paths resolve relative to the script rather than to the shell, so the whole thing runs from any directory. tools/ is a gitignored drop zone with a tracked README explaining what belongs in it. The tools are fetched, never vendored: they are large, platform specific and under their own licences. The README records the one build gotcha worth knowing, that c-chess-cli's make.py passes an x86-only flag and fails on Apple Silicon. Versions of both the runner and the opponent are now printed with the results. A figure is only reproducible against the opponent that produced it, and a different major Stockfish will move every number in doc/strength.md. Also: the runner is started in tests/. fastchess drops a resume file full of absolute paths into its working directory, and it was landing in the repo root. Disabling autosave does not stop it, and -config is a *load* directive that clobbers the engine setup if you try to use it to redirect the write - so the working directory is the lever, which is free to use now that every path handed to the runner is absolute. Verified against both runners: same games, same result, 8-14-10 either way. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>