Cap fee components before proposal validation

[AztecBot]

Summary

Fee header compression capped congestion and prover components only when storing checkpoint metadata, while proposal validation could still charge the uncapped congestion amount. That let proof-time reward distribution burn only the stored capped value and route the remainder to sequencer rewards.

Fix

• Cap fee-asset prover and congestion components in getManaMinFeeComponentsAt before summedMinFee and proposal validation use them.
• Keep FeeHeaderLib.compress defensive and update overflow tests to assert validation and storage use the same capped component values.

Testing

• FOUNDRY_PROFILE=coverage forge test --match-path test/fees/FeeHeaderOverflow.t.sol
• FOUNDRY_PROFILE=coverage forge test --match-path test/fees/FeeRollup.t.sol
• git diff --check

Issues

• Closes AztecProtocol/aztec-claude#593 — FeeHeader congestion cap silently redirects rollup burn to sequencer rewards at proof time.

---

Created by claudebox · group: l1-audit-remediation