apollo_integration_tests: add regression tests for matching the proof generation

[einat-starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[einat-starkware]

• apollo_integration_tests: add regression tests for matching the proof generation #13952 👈 (View in Graphite)
• apollo_integration_tests: test to verify proof flow fixtures #13910 : 1 other dependent PR (#13912 )
• apollo_integration_tests: add proof flow integration test #13950
• apollo_integration_tests: add shared proof-flow infrastructure #13760 : 1 other dependent PR (#13761 )
• starknet_os_flow_tests: generate a cairo pie for the integration test #13781 : 1 other dependent PR (#13782 )
• main-v0.14.2

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

[cursor]

PR Summary

Low Risk
Low risk: changes are confined to test utilities and integration/flow tests, adding assertions and refactoring constants without affecting production logic.

Overview
Adds regression coverage to keep proof-flow fixtures in sync with the current virtual-OS pipeline and versioned constants.

Promotes the proof-flow genesis global root and STRK fee token address into shared expect-test-backed constants (EXPECTED_PROOF_FLOW_GENESIS_GLOBAL_ROOT, EXPECTED_STRK_FEE_TOKEN_ADDRESS), updates chain-info construction to use them, and adds new tests that (1) ensure the fixture program hash remains in allowed_virtual_os_program_hashes and (2) verify the virtual-OS-derived fee token address and genesis global root still match what the proof-flow integration tests/fixtures expect.

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

[github-actions]

Artifacts upload workflows:

• Started at 2026-05-05T08:05:09Z
• Started at 2026-05-06T07:20:04Z
• Started at 2026-05-06T09:00:55Z
• Started at 2026-05-06T09:07:39Z
• Started at 2026-05-06T09:23:02Z
• Started at 2026-05-12T17:42:17Z
• Started at 2026-05-12T19:38:29Z
• Started at 2026-05-12T19:39:00Z
• Started at 2026-05-12T19:38:29Z

[Yoni-Starkware]

@Yoni-Starkware reviewed 3 files and all commit messages, and made 2 comments.
Reviewable status: 3 of 4 files reviewed, 2 unresolved discussions (waiting on einat-starkware).

---

crates/starknet_os_flow_tests/src/virtual_os_test.rs line 332 at r2 (raw file):

    EXPECTED_PROOF_FLOW_STRK_FEE_TOKEN_ADDRESS
        .assert_eq(&virtual_os_strk_fee_token_address.to_hex_string());
}

WDYT about moving EXPECTED_STRK_FEE_TOKEN_ADDRESS to a shared location like blockifier_test_utils?

We already have have a test for it here:

sequencer/crates/starknet_os_flow_tests/src/initial_state.rs

Line 391 in 5a4b997

EXPECTED_STRK_FEE_TOKEN_ADDRESS.assert_debug_eq(&**address);

Code quote:

fn proof_flow_chain_info_matches_virtual_os_test() {
    let virtual_os_strk_fee_token_address = block_context_for_flow_tests(BlockNumber(0), false)
        .chain_info()
        .fee_token_addresses
        .strk_fee_token_address;
    EXPECTED_PROOF_FLOW_STRK_FEE_TOKEN_ADDRESS
        .assert_eq(&virtual_os_strk_fee_token_address.to_hex_string());
}

---

crates/starknet_os_flow_tests/src/virtual_os_test.rs line 350 at r2 (raw file):

    .global_root();
    EXPECTED_PROOF_FLOW_GENESIS_GLOBAL_ROOT.assert_eq(&virtual_os_global_root.0.to_hex_string());
}

Regarding what we talked about in Slack: your proof regression test should also store these values and check that they match the consts.

Code quote:

/// Guards against drift between the genesis global root the proof-flow integration test seeds into
/// storage and the initial global root produced by the virtual OS test pipeline. Run with
/// `UPDATE_EXPECT=1` to refresh the constant in `apollo_integration_tests::state_reader`, then
/// regenerate the proof fixtures by running `cargo +nightly-2025-07-14 test -p
/// starknet_os_flow_tests --features starknet_transaction_prover/stwo_proving --release
/// generate_proof_fixtures -- --ignored`.
#[tokio::test(flavor = "multi_thread")]
async fn proof_flow_global_root_matches_virtual_os_test() {
    let (initial_state_data, []) =
        create_default_initial_state_data::<DictStateReader, 0>([]).await;
    let virtual_os_global_root = StateRoots {
        contracts_trie_root_hash: initial_state_data.initial_state.contracts_trie_root_hash,
        classes_trie_root_hash: initial_state_data.initial_state.classes_trie_root_hash,
    }
    .global_root();
    EXPECTED_PROOF_FLOW_GENESIS_GLOBAL_ROOT.assert_eq(&virtual_os_global_root.0.to_hex_string());
}

[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.}

^{Reviewed by Cursor Bugbot for commit f593e4f. Configure here.}

[einat-starkware]

@einat-starkware made 2 comments.
Reviewable status: 2 of 10 files reviewed, 2 unresolved discussions (waiting on Yoni-Starkware).

---

crates/starknet_os_flow_tests/src/virtual_os_test.rs line 332 at r2 (raw file):

Previously, Yoni-Starkware (Yoni) wrote…

WDYT about moving EXPECTED_STRK_FEE_TOKEN_ADDRESS to a shared location like blockifier_test_utils?

We already have have a test for it here:

sequencer/crates/starknet_os_flow_tests/src/initial_state.rs

Line 391 in 5a4b997

EXPECTED_STRK_FEE_TOKEN_ADDRESS.assert_debug_eq(&**address);

Good idea, moved to blockifier test utils

---

crates/starknet_os_flow_tests/src/virtual_os_test.rs line 350 at r2 (raw file):

Previously, Yoni-Starkware (Yoni) wrote…

Regarding what we talked about in Slack: your proof regression test should also store these values and check that they match the consts.

I added a test for the allowed program hashes, is that what you mean or should I add something else?

[Yoni-Starkware]

@Yoni-Starkware reviewed 8 files and all commit messages, made 1 comment, and resolved 2 discussions.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on einat-starkware).

[graphite-app]

Merge activity

• May 12, 7:39 PM UTC: Graphite rebased this pull request, because this pull request is set to merge when ready.

[einat-starkware]

@einat-starkware reviewed 1 file and all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on einat-starkware).