I mapped each of the six prose bullet points to corresponding calldata actions. Ethereum v2: action 0 sets the COMP cToken's collateral factor to 0 (matches '15%→0%' final state), action 1 pauses COMP borrows (matches 'Pause COMP Borrows'), and action 2 sets the borrow cap to 1e18 wei = 1 COMP (matches 'Borrow Cap to 1', since COMP has 18 decimals). For USDC Comet, action 3 sets the COMP borrow collateral factor to 5e17 = 50% (matches '65%→50%') and action 4 sets the supply cap to 1e23 = 100,000 COMP (18 decimals), matching the stated decrease from 900,000 to 100,000. For USDT Comet, action 6 sets the COMP collateral factor to 50% as described. Actions 5 and 7 are deployAndUpgradeTo calls on the Comet proxies, which are the standard, expected bookkeeping step required to apply Comet Configurator parameter changes — this is routine and not something a Comet-familiar reviewer would expect to be called out separately, so I did not flag it as an omission. Addresses used (COMP token, COMP cToken, USDC Comet proxy, USDT Comet proxy) are consistent with their expected mainnet addresses. No value, target, or directional mismatches were found between the prose and the decoded calldata. Overall, the proposal description faithfully and completely represents the on-chain actions.