apollo_storage,apollo_batcher_types,apollo_batcher: add commitment infos height offset query

[yoavGrs]

Expose the batcher's state commitment infos height offset (one past the
latest stored height, None when nothing is stored), backed by a storage
cursor over the state_commitment_infos table.

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

[reviewable-StarkWare]

This change is 

[yoavGrs]

• apollo_storage,apollo_batcher_types,apollo_batcher: add commitment infos height offset query #14894 👈 (View in Graphite)
• main

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

[cursor]

PR Summary

Low Risk
Additive, read-only query behind os_input with unit tests; no changes to commit or revert write paths beyond the new reader.

Overview
Adds a read-only way to learn how far state commitment infos are stored for OS input: the value is one past the latest block with stored infos, or None when the table is empty.

Storage implements get_state_commitment_infos_height_offset by scanning the state_commitment_infos table with a cursor (lower_bound / prev) and returning latest_block_number.unchecked_next(). Tests cover empty storage, multiple appends, and offset moving back after revert.

Batcher exposes the same through BatcherStorageReader, a batcher handler, and the full client RPC path (GetStateCommitmentInfosHeightOffset request/response and get_state_commitment_infos_height_offset on BatcherClient). All of this is gated on the os_input feature, alongside the existing per-block get_state_commitment_infos API.

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

[github-actions]

Artifacts upload workflows:

• Started at 2026-07-29T10:35:01Z