Treasury Management - Polygon v2 to v3 Migration

The proposal is an Aave cross-chain governance action. On mainnet, the DAO does not directly call Aave v2/v3 Polygon contracts; instead it forwards a payload (id 22) to Polygon's governance executor via the standard cross-chain bridge (forwardPayloadForExecution). This is the expected and routine mechanism for executing Polygon-side treasury actions described in the proposal (withdrawing amTokens from Aave v2 and depositing into Aave v3, plus depositing idle wMATIC/USDC). The single decoded action matches the referenced implementation contracts (AaveV2Polygon/AaveV3Polygon migration payloads) linked in the description, and the target chain (137), access level, and executor address are consistent with a legitimate Polygon governance payload dispatch. Because the actual withdraw/deposit logic executes on Polygon via the forwarded payload rather than being decoded in this mainnet calldata, we cannot line-item verify each token amount against the prose, but there is no sign of a mismatched target, unexpected recipient, or extra/missing high-level action at this level - the forwarding call is exactly what this type of proposal is expected to contain. No value, target, or scope mismatches were found between the description's stated intent and the observable calldata structure.}}```wait invalid json - fix. I must output valid JSON only. Let me redo carefully without stray text. {