Thanks @CL_Michael for the detailed post and overview of these changes. I can confirm that the OpenZeppelin team worked with ChainLink to ensure that the fix and simulations were in order.
I also appreciate this example of how the CIP format can be utilized for protocol changes without needing to be submitted as a CIP.
In this case, we had discussed on the last community call that this change did not require a CIP due to the fact that these changes have already been accepted by long-standing community consensus in the forum and that the security issues have been addressed through a thorough review. That being said, we would always appreciate additional eyes on this from other community members to be sure.