Freeze MAI/MIMATIC, set LTV -> 0 for Arbitrum, Avalanche, Polygon, Optimism v3

The description lists four chains (Arbitrum, Optimism, Polygon, Avalanche) where the MAI/MIMATIC reserve should be frozen and its LTV set to 0, and it explicitly names the pre-deployed payload addresses for Arbitrum, Optimism, and Polygon, plus a separately-noted steward address for Avalanche ('can be implemented using the pre-deployed steward'). The decoded calldata contains exactly three actions, each calling execute(address) on a mainnet governance executor with the corresponding Arbitrum, Optimism, and Polygon payload addresses — matching the addresses stated in the description exactly. Avalanche is not represented as an on-chain action in this proposal, which is consistent with the description's wording that Avalanche changes 'can be implemented using' a separate steward mechanism rather than being part of this specific governance vote's execute calls. There are no value mismatches, no unexpected targets, and no omitted high-impact actions relative to what the prose describes for the three included chains. Given the exact address matches and the fact that Avalanche's separate handling is explicitly signaled in the prose, I find no discrepancy worth flagging.