Set ACI as Emission Manager for wstETH & tBTC

The proposal description details two specific setEmissionAdmin() calls to appoint the ACI multisig as emission manager for wstETH and tBTC, naming exact contract addresses. However, the only decoded on-chain action available is a generic execute() fallback call to a single payload contract address (0xcc01d14caa28f7fb6a638587e829e7e4bf22616f), with no arguments. This is consistent with Aave's standard governance pattern where the top-level proposal action delegatecalls into a purpose-built payload contract that internally performs the specific calls described in the prose. Because the internal logic of that payload contract is not included in the decoded calldata provided, I cannot directly verify that it calls setEmissionAdmin() on the exact wstETH and tBTC emission manager addresses named in the description, nor confirm the recipient (ACI multisig) address matches exactly. Nothing in the available calldata contradicts the description, and this pattern is routine for Aave governance, so I am not flagging a discrepancy. However, confidence is low because the actual state-changing calls are not visible for direct comparison — a reviewer with access to the payload contract's bytecode/source (referenced in the description's GitHub link) would need to confirm the specific setEmissionAdmin targets and recipient match what's claimed.