starknet_os_runner: add runner config (#12141)

[dan-starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[chatgpt-codex-connector]

💡 Codex Review

sequencer/crates/starknet_os_runner/src/running/committer_utils.rs

Lines 75 to 79 in d4b090f

	if value.0 == Felt::ZERO {
	return Err(ProofProviderError::InvalidStateDiff(format!(
	"Storage deletion not allowed: try to delete storage at address {address:?}, \
	key {key:?}"
	)));

Permit zero-value storage updates in state diff validation

This check rejects any storage write where the new value is 0, but valid invoke transactions often clear slots to zero (for example, reducing a balance/allowance to empty). In the new flow, StorageProofConfig::default() enables state-change commitment generation by default, so these transactions now fail with InvalidStateDiff before proving instead of being handled normally.

---

sequencer/crates/starknet_os_runner/src/running/committer_utils.rs

Lines 84 to 88 in d4b090f

	if !state_diff.address_to_class_hash.is_empty() {
	return Err(ProofProviderError::InvalidStateDiff(format!(
	"Contract deployments not allowed: try to deploy contracts(address to class hash): \
	{0:?}",
	state_diff.address_to_class_hash

Allow class-hash updates in invoke state transitions

Rejecting any non-empty address_to_class_hash blocks valid invoke transactions that deploy contracts or replace a contract class via syscalls. Because the state-change path is the default now, these invokes are deterministically rejected as InvalidStateDiff, which makes the proving API unable to handle a real subset of supported invoke behavior.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".