Remove Frax from Isolation Mode on Aave v3 Mainnet

The proposal follows the standard Aave governance pattern: the on-chain action is a single execute() call to a dedicated payload contract, which is consistent with how BGD Labs / Aave AIPs are typically structured — the granular parameter changes (isolation mode removal, debt ceiling set to zero) are implemented inside the payload contract itself and are not individually visible in the top-level decoded calldata provided here. Because only the generic execute() call is decoded, I cannot directly verify the specific numeric parameters (debt ceiling = 0, isolation mode = false) against the calldata; however, this is the expected and routine structure for this type of proposal, and there is nothing in the decoded action that contradicts or extends beyond the description. No target mismatch, value mismatch, or extra/omitted actions are apparent given the information available. Confidence is marked low specifically because the single 'execute()' decoded action does not expose the underlying parameter-level operations, making a full line-by-line reconciliation with the prose impossible from the data given — but this limitation is typical of this proposal format and is not itself a red flag or contradiction of the description's claims of what specification changes will occur once payload is executed.