starknet_os_flow_tests: implement FuzzCallInfo::new_call

[dorimedini-starkware]

Note

Low Risk
Pure refactor in test-only fuzz harness code; behavior should remain unchanged aside from how FuzzCallInfo instances are constructed.

Overview
Adds a FuzzCallInfo::new_call constructor that centralizes initialization of call-tree nodes (including defaulting inner_calls to empty).

Updates fuzz test setup and operation application paths (init, apply for Call/LibraryCall) to use this helper instead of repeated struct literals, reducing duplication and keeping call-node creation consistent.

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

[reviewable-StarkWare]

This change is 

[dorimedini-starkware]

• starknet_os_flow_tests: add daily fuzz test seed offset #13156
• starknet_os_flow_tests: fuzz test get block hash scenario #13155
• starknet_os_flow_tests: fuzz test emit event scenario #13154
• starknet_os_flow_tests: make fuzz test Cairo1 scenarios an enum #13153
• starknet_os_flow_tests: fuzz test call/libcall bad entrypoint scenario #13152
• starknet_os_flow_tests: add revert reason verification to fuzz tests #13151
• starknet_os_flow_tests: fuzz test call undeployed scenario #13150
• starknet_os_flow_tests: move fuzz test logic to function #13149
• starknet_os_flow_tests: align fuzz call/libcall data and behavior #13148
• starknet_os_flow_tests: fuzz test sha256/keccak scenarios #13052
• starknet_os_flow_tests: fuzz test scenario filtering mechanism #13050
• starknet_os_flow_tests: fuzz test library call nonexisting class scenario #13049
• starknet_os_flow_tests: fuzz test deploy nonexisting class scenario #13048
• starknet_os_flow_tests: fuzz test send message scenario #13047
• starknet_os_flow_tests: fuzz test increment counter scenario #13046
• starknet_os_flow_tests: exhaustive fuzz test #13045
• starknet_os_flow_tests: move most fuzz test functions to context struct #13044
• starknet_os_flow_tests: move deployed fuzz test map to be static #13043
• starknet_os_flow_tests: expect initial fuzz test addresses #13042
• starknet_os_flow_tests: split fuzz test manager from context #13041
• starknet_os_flow_tests: fuzz test TODOs #12971
• starknet_os_flow_tests: long fuzz test #12970
• starknet_os_flow_tests: daily fuzz test #12969
• starknet_os_flow_tests: fuzz test debug printing #12968
• starknet_os_flow_tests: fuzz test panic scenario #12967
• starknet_os_flow_tests: fuzz test enter/exit call #12966
• starknet_os_flow_tests: fuzz test deploy scenario #12965
• starknet_os_flow_tests: fuzz test replace class scenario #12964
• starknet_os_flow_tests: fuzz test current_class_hash method #12963
• starknet_os_flow_tests: fuzz test storage write scenario #12962
• starknet_os_flow_tests: implement FuzzCallInfo::new_call #12961 👈 (View in Graphite)
• starknet_os_flow_tests: fuzz test library call scenario #12960
• starknet_os_flow_tests: fuzz test call scenario #12959
• starknet_os_flow_tests: fuzz test return scenario + infra skeleton #12958
• starknet_os_flow_tests: fuzz test implement test_revert_fuzz skeleton #12957
• starknet_os_flow_tests: fuzz test orchestrator address in contract state #12956
• starknet_os_flow_tests: fuzz test initial contracts #12955
• main-v0.14.2

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

[Yoni-Starkware]

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

[graphite-app]

Merge activity

• Mar 5, 11:30 AM UTC: Graphite rebased this pull request, because this pull request is set to merge when ready.