Decrease Slope1 Parameter for Stablecoins on Aave V3

The proposal follows Aave's standard direct-to-AIP governance pattern: the on-chain vote executes a small number of 'payload' contracts via a generic execute() fallback call, and the actual parameter changes (Slope1 rate updates across many Aave V3 markets) are encoded inside those payload contracts' bytecode, not visible in the decoded calldata provided here. All three decoded actions are simple parameterless execute() calls to Ethereum-mainnet payload addresses, consistent with the References section which links to per-network Solidity payload implementations (Ethereum, Polygon, Avalanche, Optimism, Arbitrum, Metis, Base, Gnosis, Scroll, BNB, ZkSync, etc.). Because the decoded calldata does not expose the specific interest-rate-strategy parameters being set, I cannot directly verify that each individual asset's Slope1 is being moved to exactly 9.50% or 10.50% as claimed in the specification table. However, there is nothing in the decoded actions that contradicts the description, no unexpected targets, transfers, or role grants, and the number/pattern of execute() calls is typical for this type of multi-market risk-parameter update. Given the opacity of the payload internals, I mark confidence as low rather than flagging a discrepancy, since a low-confidence result should not be treated as a red flag — it simply means the underlying calldata cannot be fully cross-checked against the granular claims in the specification table with the information available.