pub fn version(artifacts: &Artifacts) -> Result<String>Expand description
The libid-circuits release the vendored verifiers came from, read from
the pin scripts/vendor-artifacts.sh copies in as circuits.json.
A Honk verifier IS its verification key, so a consumer that names a deployment after its artifact — a CREATE3 name, say — wants this in the name: a new circuits release is a different contract and must land at a different address rather than silently replace the old one.
Errors for an Artifacts::from_dir over a raw forge out/, which
carries no pin.