Update USDG Price Feed on Aave V3 Instances

The decoded calldata contains only a single generic execute() call to a payload contract address, which is the typical Aave governance pattern: the granular logic (setAssetSources for USDG on Ethereum and X Layer, and for PT-USDG-28MAY2026) lives inside that payload contract's bytecode and is not exposed in this decoded action list. Because the actual sub-actions (target oracle contracts, specific addresses for the price cap adapters, and the PT-USDG asset update) are not visible in the provided calldata, I cannot directly verify the specific values (price cap of 1.04, adapter addresses, Chainlink feed addresses) claimed in the description against on-chain execution. There is also no visible action for the X Layer instance, though this is consistent with Aave's cross-chain governance design where a single Ethereum-based proposal can trigger execution on other chains via a bridging mechanism, so its absence here is not necessarily an omission by the proposer. Given the opacity of the single execute() action, I am marking confidence as low rather than asserting a discrepancy — there is no evidence contradicting the description, but also no way to fully confirm the specific numeric parameters or target addresses match. Per guidance, low-confidence assessments should not be surfaced as flagged discrepancies, so I report no discrepancies and an overall assessment of consistent, pending manual review of the referenced payload contract's implementation for full verification.