Treasury Management - Add to rETH Holding (resubmission)

The proposal follows Aave's standard governance v3 pattern: the top-level on-chain action does not itself perform the wETH→rETH swap; instead it forwards execution to a separate payload contract (0xdAbad81aF85554E9ae636395611C58F7eC1aAEc5, payload ID 1) which is referenced in the proposal's 'Implementation' link as the AaveV3Ethereum treasury management payload. This forwarding mechanism is boilerplate for how Aave AIPs execute and is not something the description would be expected to spell out. However, because the decoded calldata provided here only shows the forwarding call and not the internal logic of the target payload, I cannot directly verify that the payload performs exactly a wETH-to-rETH swap while retaining 100 aEthWETH as described. There is no evidence of a mismatch, target redirection, or omitted action within the visible calldata — the single action is consistent with dispatching a treasury-management payload as claimed. Given the inability to inspect the payload's internal calls, confidence in a full action-by-action comparison is low, though nothing in the available data contradicts the description.