isledecomp/Verify byte-identical builds with ReproBit

Run a cold build, verify its authenticity, and publish reports

Trust Signals

name	description	required	default
project-directory	Project directory containing reprobit.toml	—	.
toolchain-root	Path to the already-provisioned local toolchain	yes	—
compiler-transport	Locked Wine launcher for the compiler on macOS or Linux; empty on Windows	—	""
resource-transport	Locked Wine launcher for the resource compiler on macOS or Linux; empty on Windows	—	""
jobs	Maximum number of build steps to run at once	—	4
policy	Optional narrowing override; clean may narrow allow-quarantine but never broaden it	—	""
initialization-timeout	Seconds allowed to prepare each isolated build lane	—	600
compile-timeout	Seconds allowed for each compiler or resource-compiler process	—	600
link-timeout	Seconds allowed for each librarian or linker process	—	900
cleanup-timeout	Seconds allowed to stop and drain each isolated build lane	—	10
report-directory	Report directory relative to the project	—	build/reprobit-report

name	description
report-produced	Whether this run published and validated its canonical reports
accepted	Whether this run met the selected policy
clean	Whether every clean authenticity claim passed
byte-exact	Whether every selected candidate matched its reference bytes
logic-certified	Whether every intervention passed its required checks
toolchain-origin	Whether first-party program bytes came from the declared toolchain
quarantined	Whether an allowlisted reference-byte exception ran
quarantine-count	Number of declared reference-byte exceptions used by this run
quarantine-bytes	Total number of reference bytes covered by declared exceptions
quarantine-ranges	Total number of artifact ranges covered by declared exceptions
quarantine-digest	SHA-256 identity of the canonical declared exception set
total-cost	Total intervention cost for the selected targets
report-json	Path to the canonical JSON report
report-html	Path to the self-contained HTML report