feat(circuit_params): build the leaf circuit from a real program

[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 

[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 👈 (View in Graphite)
• feat(leaf_prover): pad and validate the leaf circuit against the registry #407
• 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.

[cursor]

PR Summary

Low Risk
Developer tooling and CLI contract change only; no runtime prover/verifier paths, though registry and size reports now depend on the chosen program.

Overview
circuit-params now requires --program (path to compiled Cairo JSON). The leaf verifier circuit topology is built from that program’s memory segment (M31 limbs), matching how leaf_prover encodes program_felts, instead of a fixed 128-word zero placeholder.

The loaded program is threaded through all leaf and multiverifier sizing paths (human-readable report and --registry JSON). CLI tests pass a bundled opcode test program JSON.

Breaking: callers of the circuit-params binary must supply --program; reported component sizes and preprocessed roots can change versus the old dummy program.

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