Extend stkAAVE Emissions

The decoded on-chain action is a single generic execute()/fallback() call to what appears to be an Aave governance payload contract (consistent with the standard Aave v3 payload pattern where a proposal calls execute() on a dedicated contract that then performs the detailed logic internally via delegatecall). The calldata provided does not decode the internal operations (e.g., the specific AAVE.approve() call to the Ecosystem Reserve, the emissionPerSecond read, or any configurator calls), so it is not possible to directly verify the numeric claims in the description (90-day allowance top-up formula, unchanged emission rate, no changes to cooldown/slashing) against granular calldata parameters. Nothing in the single decoded action contradicts the description, and the target contract call itself is consistent with the referenced implementation contract linked in the proposal. Because the calldata is too coarse-grained to confirm or refute the specific claims, confidence is low and no discrepancies are flagged — there is no evidence of mismatch, but also no way to fully corroborate the details from calldata alone. This is typical for Aave's payload-based governance architecture and not itself a red flag.