increase supply cap for cbETH Aave Ethereum V3

The proposal follows the standard Aave governance pattern: the on-chain action is a single delegatecall-style execute() invocation on a dedicated payload contract, and the actual parameter change (setSupplyCap) is embedded in that contract's bytecode rather than visible as explicit calldata arguments. The description includes the full Solidity source of the payload contract, which clearly shows CBETH_SUPPLY_CAP = 30_000 being applied via configurator.setSupplyCap(CBETH, CBETH_SUPPLY_CAP). This matches the prose claim of raising the cbETH supply cap from 20K to 30K. Since the decoded action list only shows the outer execute() call (as is typical for Aave AIPs where the payload logic isn't separately decoded), I cannot independently verify the internal call from the JSON alone, which lowers confidence to medium, but there is no evidence of any mismatch — target contract, function name, and asset align with the description. No numeric, target, or scope discrepancies were found, and no additional undisclosed actions appear in the calldata beyond the single expected execute() call. Given the well-known convention for these proposals and the matching provided source code, I classify this as consistent, with medium confidence due to the limited decoding depth of the calldata provided.