Package-level declarations
Types
Where archive files live: whole files as bytes, since a tar is not text.
Builds the case directory for one comparison from the engine's full structured results. Nothing here depends on time, paths or the host, so the bytes are the same on every target. The results/ file is empty: outcomes of experiments are ingested later (6d3).
A case directory in memory: relative path to canonical text, sorted by path. Every file is generated output, so the same inputs give the same bytes. The archive writer and verify of 6d4 start from archiveEntries and check; they add certificate.json, confirmed/, reproduce/ and report.html beside these files and extend the chain over results/.
A reason a case directory cannot be read or does not check out; never thrown.
The first observation whose link to the chain does not hold; ChainBroken.index counts from 0.
Why a tar archive was refused; never thrown.
UnsupportedSchema.found is null when the file has no readable schema number.