Native bridge adapters update

The proposal description details an extensive set of changes: updating Native bridge adapter contracts across 8 networks (Ethereum, Polygon, Gnosis, Metis, Arbitrum, Optimism, Base, Scroll) to add adapter naming metadata and more granular gas limit configuration, with specific addresses listed for each network/route pair. However, the decoded on-chain action set contains only a single entry: a call to execute() with no arguments on a payload contract (0x1aae19c58bb7ef3aef70d28bc6e6a7e72a62372b) on Ethereum. This is the standard pattern for Aave governance proposals, where the governance vote triggers a single payload contract whose internal bytecode performs all the detailed actions (deploying/registering adapters, setting gas limits, etc.) that are described in the prose and verifiable via the linked code diffs and tests, but which are not exposed as decoded calldata arguments here. Because the decoded action carries no argument data, I cannot directly verify the specific addresses, gas limit values, or network-by-network claims made in the description against the calldata — there is simply nothing decoded to compare them to. This is not itself a red flag (it is the normal shape of these payload-execution proposals), but it does mean my ability to confirm faithful execution is limited to trusting that the payload contract implements what the linked source code diffs show. I found no explicit mismatch (no wrong target, no contradicted value) because there is no decoded detail to contradict the prose. Given this opacity, confidence is low, and I am not flagging any discrepancy since there is no calldata detail that conflicts with the description — only an absence of granular visibility, which is expected for this proposal type and should not be treated as a warning-worthy finding by itself.