feat(leaf_prover): pad and validate the leaf circuit against the registry

[ilyalesokhin-starkware]

Type

• feature
• bugfix
• dev (no functional changes, no API changes)
• fmt (formatting, renaming)
• build
• docs
• testing

Description

Breaking changes?

• yes
• no

---

This change is 

[cursor]

PR Summary

Medium Risk
Breaking CLI/API change and proof output depends on registry correctness; wrong registry or mismatch fails at runtime via panic/assert.

Overview
leaf-prover now requires a circuit registry JSON file and uses it to pad the leaf verifier circuit and confirm the proved circuit matches a known leaf entry.

The CLI gains --circuit-registry-json. After the Cairo proof is produced, the prover resolves the leaf by trace_log_size and log_blowup_factor, pads the verifier circuit with pad_to_targets to that config’s component sizes (replacing the old multiverifier padding TODO), and asserts the circuit’s preprocessed root equals the registry’s preprocessed_root.

circuit-registry adds LogSizes → ComponentSizes, RootHex::to_le_bytes, and lookup helpers leaf_verifier / config_pad_target. Tests add registry.json, wire it into the slow CLI test, and add a fast registry_fixture_test that keeps the fixture aligned with expected output.

^{Reviewed by Cursor Bugbot for commit 52e86fa. Bugbot is set up for automated code reviews on this repo. Configure here.}

[ilyalesokhin-starkware]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(circuit_params): build the leaf circuit from a real program #409
• feat(leaf_prover): pad and validate the leaf circuit against the registry #407 👈 (View in Graphite)
• feat(circuit_params): add --registry JSON output #399
• feat(circuit_params): report multiverifier component sizes #404
• feat(circuit_params): tool to report verifier circuit component sizes #398
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[ilyalesokhin-starkware]

an alternative to #406