Ohadn/verify program builtin deployment

[ohad-nir-starkware]

Note

Medium Risk
Introduces new AIR components and witness generation paths for verify_program, affecting proof generation/verification and preprocessed trace usage; failures would surface as invalid proofs or mismatched traces.

Overview
Adds end-to-end support for a new verify_program builtin that attests to the program segment using preprocessed program columns.

The adapter now derives and injects a verify_program memory segment (covering initial_pc..initial_ap-2) into BuiltinSegments, and the AIR/prover pipelines are extended with new program_component and verify_program claims, components, witness generators, fast-deduction logic, and CASM registry entries.

Enables the builtin only when the preprocessed trace contains curr_program_* columns, updates regression expected values/test data, and adds a prove/verify test that exercises padded verify_program in the all-components layout.

^{Written by Cursor Bugbot for commit 89efde0. This will update automatically on new commits. Configure here.}

---

This change is 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

Verifier program column log_size mismatch causes verification failure

High Severity

DEFAULT_PROGRAM_LOG_LEN is 8, but program_component::LOG_SIZE is 12. The verifier's new_with_program_for_verifier doesn't call set_program_table, so ProgramColumn::new reads the default PROGRAM_TABLE (size 1 << 8 = 256), producing columns with log_size = 8. The prover creates columns matching the actual program size (expected to be log_size = 12). This causes a mismatch in log_sizes[PREPROCESSED_TRACE_IDX] and column ordering (sorted by log_size), breaking commitment scheme verification.

Additional Locations (1)

• stwo_cairo_prover/crates/common/src/preprocessed_columns/preprocessed_trace.rs#L191-L195