op-wheel reports block base fee observability incorrectly

[fallintoplace]

Summary

op-wheel defines a BlockBaseFee gauge and passes baseFee into RecordBlockStats, but RecordBlockStats currently sets BlockGas twice: once with gas used and once with the base fee. This leaves the base-fee gauge unset and overwrites the gas gauge value.

There is also a nearby status log issue where the basefee field logs status.Gas instead of status.BaseFee.

Impact

Base-fee observability from op-wheel is incorrect. Dashboards and alerts that depend on the block base-fee gauge can report stale or missing data, while the gas gauge can temporarily reflect base fee instead of gas used.

Expected behavior

• BlockGas should record gas used.
• BlockBaseFee should record the block base fee.
• The status log's basefee field should emit status.BaseFee.