Thanks for the help in hunting this down team, especially @emmtre!
It sounds like there are multiple ways to handle it. We could delete the transient on the fly… or set that DEVELOPMENT_MODE and go from there.
It does seem this is an issue with WordPress 6.3 as it isn’t specific to Local, and as mentioned above, has been on other hosts as well. I wonder if this is on the community’s radar at all? Or if this is just the new way WordPress works and changes should be made on our end to accommodate. 